Directives for error handling in Adobe Workfront Fusion

Access requirements

You must have the following access to use the functionality in this article:

Adobe Workfront plan*

Pro or higher
Adobe Workfront license*

Plan, Work
Adobe Workfront Fusion license**

Workfront Fusion for Work Automation and Integration

Product Your organization must purchase Adobe Workfront Fusion as well as Adobe Workfront to use functionality described in this article.

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

For information on Adobe Workfront Fusion licenses, see Adobe Workfront Fusion licenses.

Directives for error handling

Rollback

Scenario execution is stopped immediately and a Rollback phase is started on all the modules in an attempt to revert them all to their initial state. The subsequent modules are not processed.

Barring a few error types, 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 executions setting under Scenario settings is not checked.

Commit

Scenario execution is stopped immediately and a commit phase is started on all modules. The subsequent modules are not processed.

All unprocessed bundles are ignored.

The scenario execution status is marked as "success." For information about commit phases, see Commit in the article Scenario execution, cycles, and phases in Adobe Workfront Fusion.

Resume

A substitute output is specified and supplied to the module that encounters an error.

The subsequent modules are processed.

The scenario execution status is marked as "success."

Ignore

The error is ignored and the 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 in Adobe Workfront Fusion.

There are, however, some exceptions. For more information, see Allow storing incomplete executions in the article The scenario settings panel in Adobe Workfront Fusion.

The 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.

See the Break section below for further information.

Retry

In some cases it could be useful to re-execute a failing module for a couple of times 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 in Adobe Workfront Fusion.
NOTE

Currently the error handling directives cannot be used out of the scope of an error handling route and 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 Error handler route in the article Error handling in Adobe Workfront Fusion. Also see Workaround for Throw in the article Throw error handling in Adobe Workfront Fusion.

Break

When an error is handled by the Break directive, a record is created in the View and resolve incomplete executions in Adobe Workfront Fusion folder which stores the state of the scenario execution along with data from the prior modules. For each bundle of data that causes the error, a separate record is created.

The record references the module where the error originated and contains information regarding what data was received by the module as input. For more information, see View and resolve incomplete executions in Adobe Workfront Fusion.

Here, you may resolve the error manually by updating the scenario (if needed) and running it once.

On the other hand, by enabling the Automatically complete execution option under the Break directive settings, it can be configured to automatically process an incomplete execution by re-executing the scenario after the specified number of minutes.

With this option enabled, when an error takes place, the incomplete execution is retrieved (after the time specified in the Interval between attempts field) and executed with the original input data. This will repeat until the execution of the module completes without an error or until the Number of attempts specified is reached.

NOTE

If the initial retry attempt fails, the interval between retries increases exponentially every other attempt.

When “Automatically complete execution” is turned on, the scenario run is marked as “Success” because the Break error handler’s auto-retry is handling the issue automatically. In this case, users do not receive an email about the failed run.

When “Automatically complete execution” is turned off, the run is marked as “Warning”.

However, there are some exceptions to executions being stored under Incomplete Executions and with some error types, the auto-retry of a scenario execution is not possible. For more information, see Allow storing incomplete executions in the article The scenario settings panel in Adobe Workfront Fusion.

For additional information, see Advanced error handling in Adobe Workfront Fusion.

On this page