The Error Handling command is available via the gear button on the bottom-right of most cards in a Flow.
The error handling options are:
- Retry: “0 times” by default but can choose to try 1, 2, or 3 more times if the action of a card results in an error.
- After: “1 minute” by default – this is how long to wait before trying again if “Retry” is set to 1, 2, or 3. So, for instance, if you have an app action that fails because the app was temporarily unavailable, then retrying 5 minutes later may work. The Flow pauses during this time and then resumes if the retry succeeds.
- Then: ”Halt Flow” by default, this is the step you want the Flow to take when an error is encountered, after any retries are attempted. Options are:
- Halt Flow: Stops the Flow with an error.
- Return Values: Stops the Flow with an error, but sends a custom message back to the caller (if any) of the Flow (e.g. if the card is part of an API Endpoint Flow). You’ll be able to specify a message and add as many other fields as you’d like. For any custom fields you add, you can enter values or drag/drop an output field from earlier in the Flow into any input.
- Run Another Flow: Stops the Flow with an error, but also kicks off a Child Flow of your choice. If the Flow you choose accepts inputs, you’ll be able to enter values into those inputs or drag/drop an output field from earlier in the Flow into any input. The Flow that is called will be able to get the error details using the “Error” output field on the Child Flow card.
- Continue Flow*: There is no option in the Error Handling dialog to continue the Flow but you can accomplish this by adding an If Error block (or blocks) to your Flow, which allows you to specify steps to try and then additional steps to take to handle the error and continue the Flow.