MQTT Trigger State and Status

Each MQTT trigger has a state and a status. The state indicates whether the trigger has been set to enabled, disabled, or suspended. The status reflects the current condition of the trigger. An MQTT trigger can have a status of “Running” or “Not Running (reason)” where reason identifies why the trigger is not running, such as “Not Running (Trigger Disabled)” or “Not running (Connection Alias Failure)” For example, an MQTT trigger can have a state of Enabled and a status of Not running (Trigger Failure).

Trigger State	Description
Enabled	The MQTT trigger is running and connected to the MQTT server. Integration Server retrieves and processes messages for the MQTT trigger.
Disabled	The MQTT trigger is stopped. The MQTT trigger is not connected to the MQTT server. Integration Server neither retrieves nor processes messages for the MQTT trigger. The MQTT trigger remains in this state until you enable it. An MQTT trigger can be in a temporary disabled state which is indicated by an asterisk * after the word Disabled. An MQTT trigger can become temporarily disabled when the Stop trigger retry failure handling behavior takes effect after retry failure occurs. For more information bout retry failure handling and when Integration Server automatically enables a temporarily disabled MQTT trigger, see webMethods Service Development Help.
Suspended	The MQTT trigger is running and connected to the MQTT server but is not retrieving or processing new messages. Integration Server stopped retrieving messages from the MQTT server, stopped pulling messages from the local trigger queue for the MQTT trigger, but continues processing any messages it has already retrieved from the local trigger queue. Integration Server enables the MQTT trigger automatically upon server restart or when the package containing the MQTT trigger reloads.