Zoho Flow provides error notification settings at the flow level, which send an email to nominated addresses when an execution fails. Within the flow builder, you can configure what happens after a failed action step: stop the flow, continue to the next step, or take an alternative action such as sending a Slack alert or writing a log entry. The execution history records the error details for each failed step. For transient failures, the re-run capability lets you replay a specific failed execution once the underlying issue is resolved.
Configure error handling for any flow that handles business-critical data: invoice creation, customer record updates, order notifications, or payment processing. The more consequential a missed execution, the more important it is to have notification and fallback logic in place. For low-stakes flows such as social media post notifications, the default behaviour of logging the failure in execution history may be sufficient without additional alerting.
Distinguish between transient errors, such as a temporary API outage, and permanent ones, such as a missing required field. Transient errors may resolve themselves if you re-run the execution after a delay; permanent errors require a flow configuration fix. Avoid building re-run logic into the flow itself for permanent errors, as this creates an infinite loop. Document which flows have error notifications enabled and who receives them, so alerts do not go to a shared inbox that nobody monitors.
In the flow settings, you can enable failure notifications and specify one or more email addresses to receive alerts. These notifications are sent each time an execution fails, including a summary of the error. For more immediate alerting, you can also add an action step in the flow that sends a Slack message or an email when a preceding step fails, giving you more control over the notification content and recipients.
This depends on the configuration. By default, a failed action step stops the flow execution. However, you can configure individual steps to continue to the next step even if they fail, allowing the rest of the flow to run. This is useful when one step is non-critical, such as a logging action, and you do not want it to block the primary data sync steps that follow.
Aaxonix is a certified Zoho implementation partner based in Pune. Architecture-first, no surprises.