Set error handling for cards in flows
You can set values for error handling on most cards in Workflows.
Retries for cards in flows only take place as a result of
HTTP 429 Too Many Requests errors. You won't be able to set error handling for other HTTP errors.
- Click the Other options gear icon on a card and select Error handling.
- In the Retry dropdown, select a value for the number of times to re-execute a card if an error occurs. The default is
- In the After dropdown, select a value for the amount of time that the card will pause between retries. You may need to select a period of several minutes if a card produces an error often because an application is unavailable and more time is needed to ensure you can resume the flow without further interruption. The default is
- In the Then dropdown, select an option for what the card must do if it fails to execute. The options are
Return Values, or
Run another Flow.
- Halt Flow: Stop the flow with an error.
- Return Values: Stop the flow with an error but send a custom message to another flow. You can add fields and enter values or drag and drop outputs from earlier stages in the flow.
- Run another Flow: Stop the flow with an error, but run a helper flow. If your helper flow accepts inputs, call a flow by clicking Choose Flow and selecting a helper flow from the Select flow dialog. The flow that's called will be able to get the error details using the Error output field on the helper flow card. See Parent flows and other flow types.
Exceptions to automatic retries
There are cases when HTTP status codes that are returned by an action card will halt retries. When one of the following HTTP status codes is returned, retries will not be triggered:
These HTTP status codes generally indicate that another retry won't change the outcome of the request. See HTTP status codes.
If you need to build a flow where retries must take place after one of these HTTP status codes is returned, see If Error.