Error types

Last update: January 10, 2025

Topics:
Workfront Fusion

Sometimes an error can occur during the execution of a scenario. This usually happens if a service is unavailable due to a failure to connect to the service, or if a validation fails.

Adobe Workfront Fusion distinguishes between several basic error types. The type of error determines your Fusion scenario’s next actions.

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 package	Any
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.

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

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

Connection Error

ConnectionError

Connection errors are one of the most common errors. They are usually caused by unavailability of the third-party service for various reasons, such as overloading, maintenance, or outage. The default handling of this error depends on which module encountered the error.

If the error occurs on the first module, the execution of the scenario is terminated with a warning message. Workfront Fusion then repeatedly attempts to rerun the scenario at increasing time intervals. If all attempts fail, Workfront Fusion deactivates the scenario.
If the connection error occurs on another module than the first one, the subsequent steps depend on the Allow storing incomplete executions option in the scenario advanced settings:
- If this option is enabled, the execution of the scenario is moved to the Incomplete executions folder where Workfront Fusion repeatedly attempts to rerun the scenario at increasing time intervals. If all attempts fail, the execution will remain in the Incomplete executions folder awaiting manual resolution by the user.
  
  For more information on incomplete executions, see View and resolve incomplete executions.
- If this option is disabled, the execution of the scenario ends with an error followed by a rollback phase. Workfront Fusion then repeatedly attempts to rerun the scenario at increasing time intervals. If all attempts fail, Workfront Fusion deactivates the scenario.
For more information on the Allow storing incomplete executions setting, see Allow storing incomplete executions in the article Configure scenario settings.

Increasing time intervals

The algorithm for increasing time intervals between attempts when an error occurs is known as exponential backoff. The increasing time intervals are set as follows:

10 minutes
1 hour
3 hours
12 hours
24 hours

The increasing time intervals help prevent frequently executed scenarios from using operations on repeatedly failing attempts.

recommendation-more-help

Example:

A scenario contains the Google Sheets trigger Watch Rows. Google Sheets is unavailable for 30 minutes due to maintenance when Workfront Fusion starts the scenario, so it is unable to retrieve new rows. The scenario stops and tries again in 10 minutes. Because Google Sheets is still unavailable, Workfront Fusion is still unable to get information about new rows. The next run of the scenario is scheduled in 1 hour. Google Sheets is available again at this time, and the scenario runs successfully.

Data error

DataError

A data error is generated when an item is incorrectly mapped and does not pass the validation performed on either the Workfront Fusion side or on the side of the third-party service.

If this error occurs, the scenario, up to where the module failed, is moved to the incomplete executions folder, where you can troubleshoot the issue. However, the scenario does not stop, and continues to run according to its schedule. To stop the execution of the scenario when Data error appears, enable the Sequential processing option in the Scenario settings panel.

If you have not enabled the Allow storing incomplete executions option in the scenario settings, the execution of the scenario terminates with the error, and a rollback is performed.

Duplicate Data Error

DuplicateDataError

If Workfront Fusion tries to insert the same bundle twice into a service that does not allow duplicate data, a duplicate data error is generated. If this error occurs, Workfront Fusion proceeds in the same way as as it does for the data error.

For more information, see Data Error in this article.

Invalid Access Token Error

InvalidAccessTokenError

An invalid access token error occurs when Workfront Fusion cannot access your account registered with a third-party service. This usually happens when you revoke access rights for Workfront Fusion in the administration of a given service, but scenarios that use that service continue running according to schedule.

If this error occurs, the scenario execution stops immediately. The rest of the scenario starting from the module where the error occurred moves to the incomplete executions folder.

Rate Limit Error

RateLimitError

If a limit set by a given service is exceeded, a rate limit error is generated. If this error occurs, Workfront Fusion proceeds in the same way as it does for the Connection Error.

For more information, see Connection Error in this article.

Incomplete Data Error

IncompleteDataError

An incomplete data error occurs only with triggers. This error is generated if a trigger fails to download required data from a given service.

If a scenario terminates with the IncompleteDataError, its further behavior will depend on its setting of Max number of consecutive errors.

For more information, see Number of consecutive errors in the article Configure scenario settings.

Example:

A scenario has the Workfront trigger Watch Record set to watch for documents. The scenario executes while you are uploading a large document, such as a long video. Because Workfront Fusion tries to download the video while it is still uploading to Workfront, the scenario terminates with the IncompleteDataError.

Runtime error

RuntimeError

Any error that appears during scenario execution and is not one of these error types is reported as a RunTimeError.

If a scenario terminates with the RuntimeError, its further behavior depends on the Max number of consecutive errors setting.

For more information, see Number of consecutive errors in the article Configure scenario settings.

NOTE

If a scenario starts with an instant trigger and encounters this error, the setting of Max number of consecutive errors is ignored, and the scenario is deactivated immediately.
For more information, see Instant triggers in the article Modules overview.

Inconsistency Error

InconsistencyError

If any of these errors occurs during the commit or rollback phase, the scenario terminates with an Inconsistency Error.

If this error appears in a scenario, the execution of the scenario is immediately stopped.

Warning

While executing a scenario, you may receive a warning informing you about a problem. A warning does not prevent the scenario from completing successfully.

For example, a warning can appear when the maximum allowed file size is exceeded and the Enable data loss option is disabled.

Resources

For more information on mapping, see Mapping overview.

For information about incomplete executions, see View and resolve incomplete executions.

For information about the scenario settings panel, see Configure scenario settings.

For information about schedules, see Schedule a scenario.

For information about scenario phases, see Scenario execution, cycles, and phases.

For information on the Enable data loss option, see Enable data loss in the article Configure scenario settings.