Custom Error Handling
Custom error handling within a Flow for each step (or node a.k.a. Connector or Helper) of a Flow
Last updated
Custom error handling within a Flow for each step (or node a.k.a. Connector or Helper) of a Flow
Last updated
With custom error handling ⚠️ you can set how an error should be handled on a per-connector basis in order to prevent flows from being terminated for small errors, but also handling crucial errors accordingly.
You can set error handling on each connector of a flow by opening it and clicking the edit button next to its name, where you find a dropdown with the available options:
There are five options how to handle errors on each Connector and Helper node of a flow:
Terminating the entire flow upon an error is the default option, the connector which caused the error will get the status error, just as the flow itself.
The flow continues with the next flow step as if there wasn't an error. The flow step with the error gets the status error, the flow itself has the status success. This is helpful if you e.g. loop over hundreds of records and don't want to stop the whole flow due to one error.
Continue flow cannot be used in the last step of a loop. In this case, use Skip loop iteration in the last step of the loop instead.
Continue flow should not be used in the Boolean and Multi Case Helper, as an error will not produce one of the outputs written on the arrows and thus the flow will get stuck at that particular point.
The current loop iteration is skipped and the next iteration of that loop is started (i.e. the next 'item' of the list the looper is looping over).
There is no output saved for the loop iteration with the error in the loop itself in order to use the content of the loop in further steps, as if the error didn't happen.
The steps that happened inside the loop are shown in the flow debugger and the flow step with the error gets the status error.
In case the looper is a while loop, which has input from the flow step that failed for the while condition, the looper would fail as well, which is then handled as specified in the looper.
The (current) loop where the flow step failed is broken, which means that the inner-most loop (based on the position of the error) is terminated and the flow continues as it would if the loop was finished. In the next flow iteration of the loop around it, the loop will be executed again as usual. This could either be the next step after the loop, or if the loop is nested, the loop around the loop where the flow step failed.
The failed flow step and the current loop get the status error.
When you select Manual handling, another arrow with the label Error is added to the corresponding connector.
In case of an error in that connector, the path with the error label will be executed (this could e.g. be reconnected to the standard flow).
