What is the "Retry" Functionality?

Users may occasionally need to re-execute a failing module in the event that the reason for the failure may self-resolve over time. As there is no direct handling directive that addresses this issue, refer to the below for two workaround methods.

Using the Break directive

• In the Advanced scenario settings enable the "Allow storing of Incomplete Executions" option.
• Attach an error handler route to the module. Learn more about error handling here.
• Connect the Break directive to the error handler route and configure it per the image you see below. Learn more about error handling directives here.
• [PHOTO]

⚠️ With this method, users are to expect that the minimum retry interval is one minute. If the module is processing multiple bundles and one of them fails, the bundle that caused the error will be moved to the "Incomplete executions" folder and scheduled for retries. The current execution will continue and the module will process the subsequent bundles. 

To prevent the scenario from re-execution, enable the "Sequential processing" option within the settings of "Scenario". This allows you to pause the scenario until the moved bundle has been successfully resolved. 

Using the Repeater module

• In the Repeater module, set the Repeats field to the maximum number of attempts.
• Connect the potentially failing module to the Repeater module.
• Attach an error handler route to this module. Learn more about error handling here.
• Connect the Tools > Sleep module to the error handler route and set its Delay field to the number of seconds between the attempts.
• Connect the Ignore directive after the Tools > Sleep module. Learn more about error handling directives here.
• Connect the Tools > Set variable module after the potentially failing module. Configure the module to store the results in a variable. You may name the variable "Result". 
• Connect the Array aggregator module after the Tools > Set variable. Select the Repeater module in its Source Module field.
• Connect the Tools > Get variable module to the Array aggregator module. Configure it to obtain the value of the "Result" variable.
• Insert the Tools > Get variable module between the Repeater module, and the potentially failing module. Configure it to obtain the value of the "Result" variable.
• Insert a filter between this Tools > Get variable module and the potentially failing module. Have the filter continue only if the "Result" variable does not exist.

If the result of the potentially failing module is too complex to be stored in a simple variable, Use Data store to store or retrieve it instead. Please note that "Data store" would contain just one record.

We will continue to update this space with more workarounds for the "Retry" functionality.