Error handling
Exponential backoff
1 min
uses https //en wikipedia org/wiki/exponential backoff to automatically schedule reruns with increasing time delays the reruns trigger when a module in the outputs 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 outputs the connectionerror because the third party service is unavailable, schedules the rerunning of the one minute after the error occurs if a module during the rerun outputs the connectionerror again, schedules another rerun after 2 minutes and so on if the 8th attempt fails, disables scheduling of the until disables scheduling the , the follows the run schedule in addition to the exponential backoff reruns (though there are docid 7 hehdtuu2xyys8 qurub ) if you want to wait with scheduling the next runs until the reruns finish, enable docid\ evar6qlowv4yyuneyv 00 in settings if you enable the option to store incomplete executions in the settings, stores the run in incomplete executions then schedules reruns from the incomplete execution data if all rerun attempts fail, keeps the incomplete execution for you to resolve manually