Overview
Each node in the workflow builder has three configuration tabs: Inputs, Outputs, and Error Handling. The Error Handling tab consolidates everything related to node failures — what happens when a node fails, how errors are mapped for downstream use, and whether retries or timeouts apply. In this article, we'll be covering what the Error Handling tab contains and how to configure each option.
Open the Error Handling tab
Select any action node on the workflow canvas to open its configuration panel in the right sidebar. Click the Error Handling tab to view and configure failure behavior for that node.
The Error Handling tab is available on action nodes. Trigger nodes do not have error handling configuration.
Map error outputs
The error mapper lets you extract and rename fields from a node's error output, making them available to downstream nodes connected via an error link.
When a node fails, it produces an error object that includes an error code and additional context about the failure. Use the error mapper to pull out the fields you need — for example, the error code — and give them names that are easier to reference in subsequent logic.
For a full walkthrough of how to configure the error mapper, see Using the Error Mapper.
Skip a failed node
The skip node option allows a workflow to continue running when a node fails, instead of stopping and routing to an error link. When skip is enabled, the node is marked as skipped in the execution log and the workflow proceeds to the next step as if the node succeeded.
Use this option for non-critical steps where failure is acceptable and you don't need to branch on the error.
For more detail on when and how to use skip, see Skipping Failed Nodes.
Configure retry strategies
Retry strategies tell the workflow engine how to handle transient failures — errors that may succeed if the node is run again after a short delay. You can configure the number of retry attempts and the delay between them.
Retries are most useful for nodes that call external services, where timeouts or rate limits may cause intermittent failures.
For full configuration details, see Handling Node Failures: Retry Strategies, Timeouts, and Error Links.
Set a timeout
The timeout setting defines the maximum amount of time a node is allowed to run before it is automatically failed. If the node does not complete within the configured duration, it fails with a timeout error and the workflow routes to the error link if one is configured.
Setting a timeout prevents a slow or unresponsive external call from blocking a workflow indefinitely.
For full configuration details, see Handling Node Failures: Retry Strategies, Timeouts, and Error Links.
Related to