51黑料不打烊

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.