Error handling
Exponential backoff
1 min
{{product name}} uses https //en wikipedia org/wiki/exponential backoff to automatically schedule {{scenario singular lowercase}} reruns with increasing time delays the {{scenario singular lowercase}} reruns trigger when a module in the {{scenario singular lowercase}} outputs ratelimiterror connectionerror moduletimeouterror the time delays between the scenario reruns depend on whether docid 6zznn7v35herrcjfccp9q are enabled or not true 217,217,217 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type this means that when a module in your {{scenario singular lowercase}} outputs the connectionerror because the third party service is unavailable, {{product name}} schedules the rerunning of the {{scenario singular lowercase}} one minute after the error occurs if a module during the rerun outputs the connectionerror again, {{product name}} schedules another rerun after 2 minutes and so on if the 8th attempt fails, {{product name}} disables scheduling of the {{scenario singular lowercase}} until {{product name}} disables scheduling the {{scenario singular lowercase}} , the {{scenario singular lowercase}} follows the run schedule in addition to the exponential backoff reruns (though there are docid 7 hehdtuu2xyys8 qurub ) if you want {{product name}} to wait with scheduling the next {{scenario singular lowercase}} runs until the reruns finish, enable docid\ evar6qlowv4yyuneyv 00 in {{scenario singular lowercase}} settings if you enable the option to store incomplete executions in the {{scenario singular lowercase}} settings, {{product name}} stores the {{scenario singular lowercase}} run in incomplete executions {{product name}} then schedules {{scenario singular lowercase}} reruns from the incomplete execution data if all rerun attempts fail, {{product name}} keeps the {{scenario singular lowercase}} incomplete execution for you to resolve manually