#Why is a block in my automation failing?

Look under the block's numbers on the canvas. Once the block has had failures, the Top failure reasons alert shows up to 3 reasons, each with its number of occurrences and when it last happened. Click a reason to see who failed with it and, from there, replay the execution step by step.

Role: any member with access to the workspace.

#Before you start

• The automation must be published and have run. In draft, the canvas does not show block numbers, so the alert does not appear either.
• The alert sits with the block's numbers. Blocks that show no numbers show no alert.
• Only real executions count. Test runs are left out of the alert, the same way they are left out of the block's other numbers.

#Steps

1. Open the automation and find the block that has failures.
2. Under the block's numbers, read the Top failure reasons alert. Each row shows:
   • the reason in plain language, plus what to do about it when there is a recommended action;
   • how many times it happened;
   • when it last happened and, if it happened in the last day, how many times in the last 24h.
3. Click the reason to open the dialog with the contacts that failed with it in this block. Next to each contact you see the date of the most recent failure and, if they failed more than once, how many times (for example, 3×).
4. Click Debug next to the contact. The dialog closes and the step-by-step execution panel opens over the canvas with their most recent failure, showing where it went and where it stopped.
5. To see everyone who failed in the block, without splitting by reason, click See everyone who failed at the end of the alert. On message-sending blocks the link reads See everyone whose send failed and lists only refused messages; open that block's execution failures from the reason row.

From the same dialog you can save the group as a list to handle later. The steps are in How do I see which contacts failed with each automation error. Coming from the block alert, the list only gets the people who failed in that block.

#Why a reason with fewer occurrences comes first

The alert puts what is failing now at the top. Reasons that happened in the last 24h come first, from the most to the least frequent in that period. Older reasons come next, ordered by their total.

That way an error you already fixed last week does not hide a new one, even if it has piled up more occurrences. Reasons with a red dot and red text happened in the last 24h.

#Two kinds of failure in the same block

On message-sending blocks, the alert combines both kinds of failure and, when both show up, labels each row with its kind:

• send: the message went out and the provider refused it (invalid number, sending limit, WhatsApp 24h window closed) or reported later that it could not deliver it. A message that became a draft because an attendant was active in the conversation also shows here: it did not go out on WhatsApp and stayed in the chat for the attendant to review and send.
• execution: the automation stopped at this block, sometimes before sending anything.

On other blocks, only execution failures appear: the executions that stopped with an error at that block.

#Why the dialog lists fewer contacts than the alert count

The alert counts occurrences. The dialog lists contacts. Someone who failed more than once with the same reason, because they re-entered the automation or it retried, appears once, with the total next to them. For execution failures, only contacts the automation was able to identify are listed.

To see errors for the whole automation instead of a single block, use the Top errors card in the Executions tab.