Action Status Abnormal Alert

The Action Status Abnormal alert indicates that one or more EMQX data integration actions have remained outside the normal operating state for a period of time.

This alert does not necessarily mean that messages have been dropped. After the connector associated with the action recovers, buffered messages can usually be delivered. If messages are dropped, an Action Execution Failed alert is also triggered.

Associated Connector in an Abnormal State

Symptom

On the Data Integration page, an action remains in an abnormal or unavailable state instead of recovering.

Common Causes

The connector used by the action is unable to operate normally because of one of the following conditions:

• Network failure or instability
• Invalid authentication credentials
• Exhausted resources or quotas
• An unavailable target service, such as a database or message queue
• Inconsistent connection states across cluster nodes

Resolution

Check and repair the connector associated with the action first. For detailed guidance, see Connector Status Abnormal Alert.

After the connector returns to a normal state, the action automatically attempts to reconnect and deliver messages from its buffer.

Troubleshooting

1. Log in to the EMQX Cloud Console and enter the affected deployment.

2. Go to Data Integration -> Actions. Locate the action in an abnormal state and identify its associated connector.

3. Check the connector status. If it is Disconnected, Error, or inconsistent across cluster nodes, resolve the connector issue first.

4. Follow Connector Status Abnormal Alert to identify and resolve the connector problem.

5. After the connector status changes to Connected, verify that the action also returns to normal and begins delivering buffered messages.

Considerations

• An abnormal action status does not indicate a rule matching failure. As long as the action buffer is not full, messages are buffered while the action is unavailable.
• Buffered messages can usually be delivered after the action recovers.
• If the connector remains unavailable long enough for the action buffer to fill and requests to exceed their expiration time, older messages may be dropped.