Manage incomplete executions

when dealing with {{scenario singular lowercase}} incomplete executions, you should first decide if you want to finish the run and process the rest of the data in the {{scenario singular lowercase}} if you want to finish the {{scenario singular lowercase}} run, you should check the error that created the incomplete execution go to the incomplete executions tab find the incomplete execution and click details the scenario builder opens click the warning sign on the module that caused the error you can also check the module settings or the docid 9z2xnh lyy62cfahjfhj5 if the error is a temporary error, like the connectionerror or the ratelimiterror , you can /#retry incomplete executions retrying an incomplete execution is like another attempt to run a {{scenario singular lowercase}} the incomplete execution runs with the same module settings as when the error happened you can retry multiple incomplete executions at once if the error requires changes in the module settings or in the general scenario blueprint, you need to /#resolve an incomplete execution manually if you find out that you don't need to run the rest of the scenario, you can /#delete incomplete executions the incomplete executions tab to open the incomplete executions tab, select the {{scenario singular lowercase}} in the list of {{scenario plural lowercase}} and switch from the diagram tab to the incomplete executions tab in the {{scenario singular lowercase}} 's incomplete executions tab, you can find the following information for each incomplete execution selection check box you can select incomplete executions to either retry or delete you can select multiple incomplete executions, or you can use the check box in the table header to select or de select all incomplete executions of a {{scenario singular lowercase}} incomplete execution id a unique text generated by {{product name}} to identify the incomplete execution you can use the incomplete execution id with the docid\ g7vz7fysaoicjddxzcncz or with the https //developers make com/api documentation/api reference/incomplete executions created the date and time when {{product name}} created the incomplete execution size the size of the incomplete execution blueprint and the data that the module was processing when it failed status possible incomplete execution statuses are unresolved the incomplete execution is not set to retry and hasn't been resolved to fix this, you can /#retry incomplete executions or /#resolve an incomplete execution the incomplete execution pending the incomplete execution is set to retry check the scheduled in column to see approximately when {{product name}} will retry the incomplete execution in progress {{product name}} is currently retrying the incomplete execution resolved the incomplete execution has been resolved successfully {{product name}} will delete the resolved incomplete execution automatically after 30 days scheduled in the approximate time until {{product name}} will retry the incomplete execution attempts the number of attempts already made to resolve the incomplete execution detail the detail of the incomplete execution opens the scenario builder with the incomplete execution in the incomplete execution detail, you can check the cause of the incomplete execution and /#resolve an incomplete execution retry incomplete executions retrying incomplete executions runs the incomplete execution again, starting with the module that caused the error retried incomplete executions run with the same configuration as when the error happened, so a retry works best for temporary errors, like the ratelimiterror or the connectionerror to retry incomplete executions make sure that the {{scenario singular lowercase}} is active you can retry incomplete executions only when the {{scenario singular lowercase}} is active to activate a {{scenario singular lowercase}} , go back to the diagram tab or the scenario builder and click the switch next to {{scenario singular lowercase}} scheduling on the {{scenario singular lowercase}} toolbar go to the incomplete executions tab select incomplete executions you want to retry you can use the checkbox at the top of the incomplete executions table to either select or de select all incomplete executions of the {{scenario singular lowercase}} click the retry selected button to retry the incomplete executions the status of the selected incomplete executions turns into scheduled in, and to in progress when {{product name}} starts retrying them if you are retrying a lot of incomplete executions, it might happen that some of them get scheduled for later processing instead the scheduled in column contains the information of when approximately {{product name}} retries the incomplete execution if the incomplete execution is resolved successfully, the status of the incomplete execution turns into resolved otherwise, the status stays unresolved resolve an incomplete execution some errors create incomplete executions that require manual changes before the incomplete execution can be resolved for example, the runtimeerror and dataerror most of the time have to be resolved manually instead of retrying you can resolve an incomplete execution manually either from the {{scenario singular lowercase}} run history, or from the incomplete executions tab you might want to check the {{scenario singular lowercase}} execution log first to investigate why the error happened go to the history tab locate the failed execution log and click details click the module that has a warning status click resolve make redirects you to the incomplete execution check the module that caused the error and fix it save the updated module settings with the save button click run once the incomplete execution runs again, starting with the module that caused the incomplete execution with the original input if the run succeeds, the incomplete execution is resolved otherwise, if resolving fails on the same module, the incomplete execution is not resolved you need to fix all errors on the module to resolve the incomplete execution if the incomplete execution fails on a different module, {{product name}} creates a new incomplete execution, starting with the module that caused the new error if you want to go directly to the incomplete execution go to the incomplete executions tab find the incomplete execution and click details check the module that caused the error and fix it save the updated module settings with the save button click run once the incomplete execution runs again, starting with the module that caused the incomplete execution with the original input if the run succeeds, the incomplete execution is resolved otherwise, if resolving fails on the same module, the incomplete execution is not resolved you need to fix all errors on the module to resolve the incomplete execution if the incomplete execution fails on a different module, {{product name}} creates a new incomplete execution, starting with the module that caused the new error delete incomplete executions when you don't need to finish the {{scenario singular lowercase}} workflow, or you don't need the data from the incomplete execution anymore, you can delete the incomplete exectution to delete incomplete executions go to the incomplete executions tab select incomplete executions you want to delete you can use the checkbox at the top of the incomplete executions table to either select or de select all incomplete executions of the {{scenario singular lowercase}} click the button delete selected to delete the incomplete executions the deleted incomplete executions are no longer in the list of incomplete executions once you delete an incomplete execution, it cannot be put back