A trigger isn’t an execution component. It is a configuration element. It doesn’t run nor can it be idle. It is used by IS run-time to establish subscriptions on the Broker and to determine which service(s) to call when documents are available on the Broker.
You’ll want to check the last time the service that the trigger is configured to use was called. This is viewable in the “Service Usage” page in Administrator. If you’re using MWS and have audit logging turned on for the you can also see execution times there.
#Universal-Messaging-Broker#Broker-JMS#webMethods#Integration-Server-and-ESB