Directives for Error Handling

Last update: Tue Dec 17 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

Topics:
Workfront Fusion

Error handling directives allow you to choose what occurs when a scenario encounters an error.

Access requirements

Expand to view access requirements for the functionality in this article.

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: Select or Prime Workfront plan: Your organization must purchase 蜜豆视频 Workfront Fusion. Ultimate Workfront plan: Workfront Fusion is included. Or Current: Your organization must purchase 蜜豆视频 Workfront Fusion.

To find out what plan, license type, or access you have, contact your Workfront administrator.

For information on 蜜豆视频 Workfront Fusion for information about 蜜豆视频 Workfront Fusion licenses, see 蜜豆视频 Workfront Fusion licenses.

Directives for error handling

The following error handling directives are available in Workfront Fusion.

Rollback

Scenario execution is stopped immediately.
A Rollback phase is started on all the modules, in an attempt to revert them all to their initial state.
Subsequent modules are not processed.
In most cases, the scenario is deactivated after the number of consecutive errors specified under Scenario settings. For more information, see Number of consecutive errors.
The scenario execution status is marked as "Error."

Note: This is the default behavior if no error handler route is attached to the module and the Allow storing incomplete executionsAllow storing incomplete executions setting under Scenario settings is not checked.

Commit

Scenario execution is stopped immediately.
A Commit phase is started on all modules.
Subsequent modules are not processed.
All unprocessed bundles are ignored.
The scenario execution status is marked as "success."

Resume

A substitute output is specified and supplied to the module that encounters an error.
Subsequent modules are processed.
The scenario execution status is marked as "success."

Ignore

The error is ignored.
Subsequent modules are not processed.
If there are unprocessed bundles, the scenario execution continues normally.
The scenario execution status is marked as "success."

Break

The state of the scenario execution is stored in the queue of incomplete executions where the error can be resolved manually. For more information, see View and resolve incomplete executions.

There are, however, some exceptions. For more information, see Allow storing incomplete executions in the article Configure scenario settings.
Subsequent modules are not processed.
If there are unprocessed bundles, the scenario execution continues normally.
The scenario execution status is marked as "warning" when the Automatically complete execution option is disabled.

For more information, see the Break section in this article

Retry

In some cases it may be useful to re-execute a failing module when there is a chance that the reason for the failure might pass over time.

Workfront Fusion currently does not offer the Retry directive, though several workarounds can be employed to mimic its functionality. For more information, see Retry error handling.

NOTE

Error handling directives cannot be used outside of an error handling route.
Workfront Fusion currently does not offer a Throw module that would enable you to easily conditionally generate (throw) errors, though a workaround can be employed to mimic its functionality.

For more information, see Configure throw error workaround.

Resources

For information on rollback and the Rollback phase, see Rollback in the article Scenario execution, cycles, and phases.
For information on the Commit phase, see Commit in the article Scenario execution, cycles, and phases.

recommendation-more-help

7e1891ad-4d59-4355-88ab-a2e62ed7d1a3