Failure events

Select the required events when configuring a webhook. An error event describes agent execution or message sending, not necessarily a failure to deliver the webhook itself.

Which events to select

Agent execution failures and message sending failures are independent events. Select both error and message_undelivered to monitor both stages. An automation can call an agent or send a message directly; the same events apply in these cases.

Event fields

The data of error and message_undelivered events includes error_code, error_message, and error_message_key, along with the available context: agent_id, sender_type, sender_id, message_event_id, response_id, automation_id, version_id, run_id, task_id, and node_id. message_event_id identifies the outgoing message when sending fails. The reason text may be absent: use error_code for programmatic handling; error_message_key identifies the localization key for an agent error. Internal stack traces and full AI provider responses are not included.

The data of automation_step_failed includes automation_id, version_id, run_id, task_id, node_id, the captured step name node_name, and error_code, error_message, occurred_at, and retryable: false. A message sending step may also provide message_event_id. The common dialog_id, lead_id, and channel_id fields are populated when that context exists; an automation without a dialog can also send this event.

Intermediate failed attempts, test runs, and an HTTP step following a connected Error branch do not produce automation_step_failed. A step failure does not mean that other parallel branches stop. One failure can produce two distinct events: for example, message_undelivered followed by automation_step_failed when unsuccessful sending causes an automation step to fail. Redelivery preserves the same event_id; manually retrying a step creates a new task and can produce a new event.

Check whether your server received these events in delivery history.