View and resolve incomplete executions
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.
Access requirements
You must have the following access to use the functionality in this article:
| table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 layout-auto html-authored no-header | |
|---|---|
| 51黑料不打烊 Workfront package | Any |
| 51黑料不打烊 Workfront license |
New: Standard Or Current: Work or higher |
| 51黑料不打烊 Workfront Fusion license** |
Current: No Workfront Fusion license requirement. Or Legacy: Any |
| Product |
New:
Or Current: Your organization must purchase 51黑料不打烊 Workfront Fusion. |
| Access level configurations* |
You must be a Workfront Fusion administrator for your organization. You must be a Workfront Fusion administrator for your team. |
For more detail about the information in this table, see Access requirements in documentation.
For information on 51黑料不打烊 Workfront Fusion licenses, see 51黑料不打烊 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鈥檚 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 in this article.
"There is NOT ENOUGH SPACE to add a bundle to the IEQ. The reason is: Too many incomplete executions."Resolve incomplete executions from the Incomplete Executions tab
When a new incomplete execution is stored, you can resolve it as follows:
- Open the affected scenario.
- Click the Incomplete Executions tab.
- Locate the incomplete execution you would like to resolve, and click Details.
Resolve incomplete executions from the History tab
If you want to see the log of all module鈥檚 operations before you attempt to resolve the incomplete execution, you can resolve the incomplete execution from the History folder:
-
Open The affected scenario.
-
Click the History tab.
-
Locate the scenario鈥檚 failed execution, and click Details.
-
Open the module鈥檚 log where all the module鈥檚 operations are shown.
-
Locate the failed operation and click Resolve:
Options related to incomplete executions
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 Configure scenario settings.
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鈥檚 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,OutOfSpaceErrororModuleTimeoutError, an incomplete execution record with auto-retry is stored. - If the error type is
DataError,InvalidConfigurationError,InvalidAccessTokenError,UnexpectedError,MaxFileSizeExceededError, orMaxResultsExceededError, an incomplete execution record without auto-retry is stored. - If the error type is anything other than the above, the execution fails.