DocumentationWorkfrontWorkfront Guide

View and resolve incomplete executions in Adobe Workfront Fusion

Last update: Fri Aug 09 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • User

The Incomplete executions folder stores scenario executions that were not successfully finalized due to an error. Each stored incomplete execution can be resolved either manually or automatically.

NOTE
By default the storing of incomplete executions is disabled. To enable it, enable the Allow storing incomplete executions option in the scenario advanced settings.
For more information about scenario settings, see The scenario settings panel 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**

Current license requirement: No Workfront Fusion license requirement.

Or

Legacy license requirement: Workfront Fusion for Work Automation and Integration, Workfront Fusion for Work Automation

Product

Current product requirement: If you have the Select or Prime Adobe Workfront Plan, your organization must purchase Adobe Workfront Fusion as well as Adobe Workfront to use functionality described in this article. Workfront Fusion is included in the Ultimate Workfront plan.

Or

Legacy product requirement: 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.

View incomplete executions

If a module encounters an error during its operation, a new incomplete execution is added to the Incomplete executions folder. Each incomplete execution contains the scenario’s blueprint and all the bundles that can be mapped into the failed module. The list of incomplete executions can be opened by clicking on the Incomplete Executions tab on the scenario detail page.

For more information, see Errors resulting into incomplete executions.

NOTE
The current size limit of the unresolved incomplete executions folder per organization is 500 MB. If your organization exceeds this limit, you may see the following error:
"There is NOT ENOUGH SPACE to add a bundle to the IEQ. The reason is: Too many incomplete executions."
For more information, see Enable data loss in The scenario settings panel in Adobe Workfront Fusion.

Resolve incomplete executions

When a new incomplete execution is stored, you can resolve it as follows:

  1. Click the Incomplete Executions tab.

  2. Locate the incomplete execution you would like to resolve and click Detail.

    If you want to see the log of all module’s operations before you attempt to resolve the incomplete execution, you can resolve the incomplete execution from the History folder:

  3. Click the History tab.

  4. Locate the scenario’s failed execution log and click Details.

  5. Open the module’s log where all the module’s operations are shown.

  6. Locate the failed operation and click Resolve:

The following options in the Scenario settings panel determine if and how the incomplete executions are stored:

  • Allow storing incomplete executions
  • Sequential processing
  • Enable data loss

For more information about these options, see The scenario settings panel in Adobe Workfront Fusion.

Errors resulting into incomplete executions

There are several categories of errors which result into storing of incomplete executions. These may include:

  • Validation errors arising from incomplete or erroneous data, mostly because of a missing item that is expected in order to successfully process all data going through a module.
  • Errors occurring from the final destination’s unavailability because of temporary or long term connection failure (for example, during connection to email or remote FTP server).

If an error occurs on the first module in the scenario, the execution stops immediately and no incomplete execution is stored.

If an error occurs on any other module and there is no error handler route attached, one of the following occurs:

  • If the error type is ConnectionError, RateLimitError, OutOfSpaceError or ModuleTimeoutError, an incomplete execution record with auto-retry is stored.
  • If the error type is DataError, InvalidConfigurationError, InvalidAccessTokenError, UnexpectedError, MaxFileSizeExceededError, or MaxResultsExceededError, an incomplete execution record without auto-retry is stored.
  • If the error type is anything other than the above, the execution fails.
recommendation-more-help
5f00cc6b-2202-40d6-bcd0-3ee0c2316b43