Configure throw error workaround

Last update: March 14, 2025

In some cases, you may want to forcibly stop the scenario execution followed by Rollback or Commit phase, or to stop the processing of a route and optionally store it in the queue of incomplete executions.

Currently, the error handling directives cannot be used out of the scope of an error handler route, and Adobe Workfront Fusion does not offer a module that would enable you to easily conditionally generate (throw) errors.

You can use the following workaround to mimic throw error functionality.

For information on incomplete executions, see View and resolve incomplete executions in Adobe Workfront Fusion.

For information on error handling directives, see Directives for error handling in Adobe Workfront Fusion.

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:

Adobe Workfront packageAny
Adobe Workfront license

New: Standard

Or

Current: Work or higher

Adobe Workfront Fusion license**

Current: No Workfront Fusion license requirement

Or

Legacy: Any

Product

New:

  • Select or Prime Workfront Plan: Your organization must purchase Adobe Workfront Fusion.
  • Ultimate Workfront Plan: Workfront Fusion is included.

Or

Current: Your organization must purchase Adobe Workfront Fusion.

For more detail about the information in this table, see Access requirements in documentation.

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

Workaround for throw

To conditionally throw an error, you can configure a module to make it purposely fail during its operation. One possibility is to employ the JSON > Parse JSON module, configured to optionally throw an error (BundleValidationError in this case):

JSON error

You can then attach one of the error handling directives to the error handling route:

  • Rollback: Force the scenario execution to stop and perform the rollback phase.
  • Commit: Force the scenario execution to stop and perform the commit phase.
  • Ignore: Stop the processing of a route.
  • Break: Stop the processing of a route and store it in the queue of incomplete executions folder.

The following example shows the use of the Rollback directive:

Rollback directive

Previous pageAdd filtering and nesting to error handling routes
Next pageConfigure retry error handling workaround

Workfront