ÃÛ¶¹ÊÓƵ

Error processing in ÃÛ¶¹ÊÓƵ 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 a service or if a validation fails. This article discusses the common errors that you may encounter.

ÃÛ¶¹ÊÓƵ Workfront Fusion distinguishes between several basic error types. It will react differently depending upon on the type of error that occurred.

Access requirements

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

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

For information on ÃÛ¶¹ÊÓƵ Workfront Fusion licenses, see ÃÛ¶¹ÊÓƵ Workfront Fusion licenses.

Connection Error

ConnectionError

Connection error is one of the most common errors usually caused by unavailability of the third-party service for various reasons (overloading, maintenance, outage, and so on). The default handling of this error depends on which module it was encountered on:

Increasing time intervals

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

The main reason for employing the increasing time intervals in Workfront Fusion is to prevent frequently executed scenarios from consuming operations on repeatedly failing attempts.

Data error

DataError

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

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.

For more information on mapping, see Map information from one module to another in ÃÛ¶¹ÊÓƵ Workfront Fusion.

For information about incomplete executions, see View and resolve incomplete executions in ÃÛ¶¹ÊÓƵ Workfront Fusion.

For imformation about the scenario setting panel, see The scenario settings panel in ÃÛ¶¹ÊÓƵ Workfront Fusion.

For information about schedules, see Schedule a scenario in ÃÛ¶¹ÊÓƵ Workfront Fusion.

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.

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 related scenarios keep running according to schedule.

If this error occurs, the execution of a scenario is stopped immediately. The rest of the scenario starting from the module where the error occurred is moved to the incomplete executions folder.

For information about incomplete executions, see View and resolve incomplete executions in ÃÛ¶¹ÊÓƵ Workfront Fusion.

Rate Limit Error

RateLimitError

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

For more information, see Connection Error.

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 The scenario settings panel in ÃÛ¶¹ÊÓƵ Workfront Fusion.

Run time error

RuntimeError

If any other error (not mentioned above) appears during scenario execution, it is reported as a RunTimeError.

If a scenario terminates with the RuntimeError, 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 The scenario settings panel in ÃÛ¶¹ÊÓƵ Workfront Fusion.

Inconsistency Error

InconsistencyError

If any error described above occurs during the commit or rollback phase, a scenario will terminate with Inconsistency Error. For more information, see Scenario execution, cycles, and phases in ÃÛ¶¹ÊÓƵ Workfront Fusion.

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. However, it does not prevent the scenario from being successfully completed.

For example, a warning can appear when the maximum allowed file size is exceeded and the Enable data loss option is disabled. For more information, see Enable data loss in the article The scenario settings panel in ÃÛ¶¹ÊÓƵ Workfront Fusion.