Using the Catch Exception Step
- 12 Mar 2021
- 1 Minute to read
- Print
- DarkLight
Using the Catch Exception Step
- Updated on 12 Mar 2021
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Example Lab Article
While Example Lab projects are resources for public use, articles and assets are not actively maintained. Screenshots and features are from the specified version below. These references may become dated as new versions are released.
Overview
Example Lab Details | |
| Version | 6.9.2 |
| Root Folder | Example Lab - Catch Exception |
| Modules | None |
| Dependencies | None |
This Example Lab project demonstrates the ability to catch an exception and continue the Flow without stopping.
Explanation
This Flow is built to demonstrate how the Catch Exception step works. The Sub-Flow is setup with an email step that has not been configured, so although the Flow steps are connected an error would still be expected since there is no configuration data. The 'Add Outcome for Exception' checkbox can be found in the Outcome section of most Flow steps; enabling this checkbox will create an On Exception outcome path from the step selected (the Run Sub-Flow step in this case).
This new outcome path leads to a Throw Exception step, which works in tandem with the Catch Exception step. Throw Exception will toss that exception data over to Catch Exception, and in this example, is received by the Save Error Log step.
Reference Articles
Project Download
The examples attached were developed to be instructional and were not developed as officially supported components. For more information or to engage our service team to develop fully supported, production quality solutions, please contact services@decisions.com. Import the project below to a Decisions environment on version 6.9.2 or later using our Importing/Exporting article.
Was this article helpful?
