In some cases it is useful to re-execute a failing module if there is a chance that the reason for the failure might pass over time.
You must have the following access to use the functionality in this article:
|Adobe Workfront plan*||
Pro or higher
|Adobe Workfront license*||
|Adobe Workfront Fusion license**||
Current license requirement: No Workfront Fusion license requirement.
Legacy license requirement: Workfront Fusion for Work Automation and Integration
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.
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.
Adobe Workfront Fusion currently does not offer the Retry error handling directive, though two workarounds can be employed to mimic its functionality. For more information, see Directives for error handling in Adobe Workfront Fusion.
In the scenario settings panel, enable the Allow storing of Incomplete Executions option.
For more information, see The scenario settings panel in Adobe Workfront Fusion.
Attach an error handler route to the module, as described in Error handling in Adobe Workfront Fusion.
Link the Break directive to the error handler route and configure it.
For more information, see Directives for error handling in Adobe Workfront Fusion.
The minimum retry interval is one minute.
If the module is processing multiple bundles and the processing of a bundle fails, the partial execution (only the bundle that caused the error) is moved to the incomplete executions folder and scheduled for retries according to the Break directive settings. However, the current execution continues and the module continues to process the subsequent bundles. You can enable the “Sequential processing” option in the Scenario settings to prevent the scenario from executing again until the execution stored in the the Incomplete executions folder has been successfully resolved.
For more information on incomplete executions, see View and resolve incomplete executions in Adobe Workfront Fusion.
Employ the Repeater module and set its Repeats field to the maximum number of attempts.
Link the potentially failing module to the Repeater module.
Attach an error handler route to this module (see Error handling in Adobe Workfront Fusion).
Link the Tools > Sleep module to the error handler route and set its Delay field to the number of seconds between the attempts.
Link the Ignore directive after the Tools > Sleep module (see Directives for error handling in Adobe Workfront Fusion).
Link the Tools > Set variable module after the the potentially failing module and configure it to store the module’s result in a variable named, for example,
Link the Array aggregator module after the Tools > Set variable and choose the Repeater module in its Source Module field.
Link the Tools > Get variable module to the Array aggregator module and configure it to obtain the value of the
Insert the Tools > Get variable module between the Repeater module and the potentially failing module and configure it obtain the value of the
Insert a filter between this Tools > Get variable module and the potentially failing module to continue only if the
Result variable does not exist.
Example: Here is a sample scenario where the HTTP >Make a request module represents the potentially failing module:
If the result of the potentially failing module is too complex to be stored in a simple variable, you can employ a data store to store/retrieve the result. The data store would contain just one record. The record’s key can be, for example,
For more information on data stores, see Data Stores in Adobe Workfront Fusion
This workaround might appear a bit too complex, and is also more demanding in terms of operations.