How to Add Error Handling to a Flow and Continue Execution When an Error Occurs
Okta Workflows how-to guides are questions and answers from weekly community office hours, MacAdmins Workflows Slack channel, and other places. Read all previous how-to guides.
On to the question.
How to add error handling to a flow and continue execution when an error occurs?
When a card execution fails, the flow execution will stop. Any cards after the error card will not be executed.
For example, in the screenshot below, API call fails, the flow stops executing and the Assign card is not processed.
Another example where flow execution stops is when Read User card results in an error (when providing an invalid user ID).
You want to be able to gracefully handle the error and continue the flow execution. To do that use the Error Handling – If Error card.
The If Error card has two sections: Try and If Error. You will try something and if it fails, the if error logic will be called and will allow you to continue the flow execution.
Using the API example from above, this is how the Try section looks. You place cards inside the Try section.
This is how the If Error section looks. You add any cards to process the error.
The If Error card allows to define output. Based on which path is taken, the Number will be set to either 100 or -100.
Tip: Learn how to create outputs for an If/Else card
How-to Guide: How to Handle an External API Call Error in Workflows
If the flow generates an error, the If Error card handles the error and the flow execution continues. The Assign card outside of If Error was processed.
In the same way you can place Read User inside the Try section of If Error card.
Even though the Read User cards results in an error the flow execution continues. The Assign card outside of If Error was processed.
Published on Java Code Geeks with permission by Max Katz , partner at our JCG program. See the original article here: How to Add Error Handling to a Flow and Continue Execution When an Error Occurs Opinions expressed by Java Code Geeks contributors are their own. |
