Add error handling
Errors can occur during the execution of a scenario.
For example, an error can occur because:
- A service is unavailable due to a failure
- A service responds with unexpected data
- Validation of input data fails
- Other reasons
If a module encounters an error during the scenario execution, and there is no error handling route attached to the module, the default error handling logic executes.
By adding an error handler route to a module, you can replace the default error handling logic with your own. ÃÛ¶¹ÊÓƵ Workfront Fusion offers five different directives that can be inserted at the end of your error handler routes.
For more information on default error handling, see Error types.
For more information on error handling directives, see Directives for error handling.
Access requirements
You must have the following access to use the functionality in this article:
| table 0-row-2 1-row-2 2-row-2 3-row-2 layout-auto html-authored no-header | |
|---|---|
| ÃÛ¶¹ÊÓƵ Workfront package | Any |
| ÃÛ¶¹ÊÓƵ Workfront license |
New: Standard Or Current: Work or higher |
| ÃÛ¶¹ÊÓƵ Workfront Fusion license** |
Current: No Workfront Fusion license requirement. Or Legacy: Any |
| Product |
New:
Or Current: Your organization must purchase ÃÛ¶¹ÊÓƵ Workfront Fusion. |
For more detail about the information in this table, see Access requirements in documentation.
For information on ÃÛ¶¹ÊÓƵ Workfront Fusion licenses, see ÃÛ¶¹ÊÓƵ Workfront Fusion licenses.
Add an error handler
To add an error handler to a module:
-
Click the Scenarios tab in the left panel.
-
Select the scenario where you want to add an error handling route.
-
Click anywhere on the scenario to enter the Scenario editor.
-
Right click the module after which you want to add an error handler route, and select Add error handler:
An error handler route is added to the module. If the module is the last module in a route, the error handler directlys follow the module. If the module has more modules after it, a separate error handler route is added.
The error handling module shows a list of Directives as well as the apps being used in your scenario.
-
Select one of the directives.
Or
Add one or more modules to the error handler route.
If you add more modules to the route, the Ignore directive is applied by default. If there is an error, the subsequent modules on that route are processed.
For more information on directives, see Error handling directives in this article.
-
(Optional) Add a filter to the error handling route. For instructions, see Add filtering and nesting to error handling routes.
Error handling directives
The directives are briefly explained below. For more information, see Directives for error handling.
There are five directives, which can be grouped into the following categories based on whether a scenario execution continues after the error.
The following directives ensure that a scenario execution continues:
-
Resume: Allows you to specify a substitute output for the module with the error. The scenario execution status is marked as success.
-
Ignore: ignores the error. The scenario execution status is marked as success.
-
Break: Stores the input to the queue of incomplete executions. The scenario execution status is marked as warning.
For more information, see View and resolve incomplete executions.
If a scenario execution should stop when an error occurs, use one of the following directives:
- Rollback: Stops the scenario execution immediately and marks its status as error.
- Commit: Stops the scenario execution immediately and marks its status as success.
Resources
For more information on error handling, see: