Incomplete executions

14min
Incomplete executions are a safety feature that protects your  from stoppoing due to errors and from data loss that could happen. When a  encounters an error with incomplete executions enabled,  stores the unfinished scenario run in the Incomplete executions tab.
Incomplete executions are disabled by default. To store incomplete executions, enable the Allow storing incomplete executions option in the scenario settings.
﻿ automatically retries specific incomplete executions:
Incomplete executions caused by the RateLimitError and ConnectionError.
Incomplete executions created by the Break error handler﻿, if you enable automatic completion of the incomplete executions.
If  doesn't retry an incomplete execution automatically, you can fix the  and retry the  run manually.
The maximum number of incomplete executions from all  in all teams in an organization depends on your usage allowance. If the limit is exceeded, you will get the following error: 
﻿
The incomplete executions tab
To open the incomplete executions tab, select the  in the list of  and switch from the Diagram tab to the Incomplete executions tab.
﻿
In the '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 .
Incomplete execution ID: A unique text generated by  to identify the incomplete execution. You can use the incomplete execution ID with the Make app﻿ or with the Make API.
Created: The date and time when  created the incomplete execution.
Size: The size of the incomplete execution blueprint.
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﻿ or manually resolve﻿  the incomplete execution.
Pending: The incomplete execution is set to retry. Check the Scheduled in column to see approximately when  will retry the incomplete execution.
In progress:  is currently retrying the incomplete execution.
Resolved: The incomplete execution has been resolved successfully.  will delete the resolved incomplete execution automatically after 30 days.
Scheduled in: The approximate time until  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  editor with the incomplete execution. In the incomplete execution detail, you can check the cause of the incomplete execution and resolve the incomplete execution﻿.
Automatic retry of incomplete executions
﻿ checks the origin of every incomplete execution when they are created. Incomplete executions that have been created because of:
RateLimitError
ConnectionError
ModuleTimeoutError
are automatically retried by  with the incomplete executions backoff﻿ at the following intervals:
1 minute (1 minute after the original scenario run).
10 minutes (11 minutes after the original scenario run).
10 minutes (21 minutes after the original scenario run).
30 minutes (51 minutes after the original scenario run).
30 minutes (1 hour 21 minutes after the original scenario run).
30 minutes (1 hour 51 minutes after the original scenario run).
3 hours (4 hours 51 minutes after the original scenario run).
3 hours (7 hours 51 minutes after the original scenario run).
If a retry attempt succeeds,  marks the incomplete execution as Resolved and stops retrying.
If all of the retry attempts fail,  marks the incomplete execution Unresolved. You can then retry the incomplete execution when the app that caused the error is available again or you can resolve the incomplete execution manually.
Other error types﻿ usually require changes in the incomplete execution and manual resolving﻿.  doesn't retry these error types automatically by default.
In addition,  automatically retries incomplete executions created with the Break error handler﻿ with the automatic run completion enabled. The number of retries and the delays between them depend on the Break error handler settings.
Manage incomplete executions
When dealing with  incomplete executions, you should first decide if you want to finish the run and process the rest of the data in the . If you want to finish the  run, you should check the error that created the incomplete execution:
1
Go to the Incomplete executions tab.
2
Find the incomplete execution and click Details. The  editor opens.
3
Click the warning sign on the module that caused the error. You can also check the module settings or the scenario execution history﻿.
﻿
If the error is a temporary error, like the ConnectionError or the RateLimitError, you can retry the incomplete executions﻿. Retrying an incomplete execution is like another attempt to run a . 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 the incomplete execution manually.
If you find out that you don't need to run the rest of the scenario, you can delete the 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:
1
Make sure that the  is active. You can retry incomplete executions only when the  is active.
To activate a , go back to the Diagram tab or the  editor and click the switch next to  scheduling on the  toolbar:
﻿
﻿
﻿
2
Go to the Incomplete executions tab.
3
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 .
4
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  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  retries the incomplete execution.
5
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  run history, or from the incomplete executions tab:
You might want to check the  execution log first to investigate why the error happened:
1
Go to the History tab.
2
Locate the failed execution log and click Details.
﻿
3
Click the module that has a warning status.
﻿
4
Click Resolve. Make redirects you to the incomplete execution.
﻿
5
Check the module that caused the error and fix it.
6
Save the updated module settings with the Save button.
7
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,  creates a new incomplete execution, starting with the module that caused the new error.
If you want to go directly to the incomplete execution:
1
Go to the Incomplete executions tab.
2
Find the incomplete execution and click Details.
3
Check the module that caused the error and fix it.
4
Save the updated module settings with the Save button.
5
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,  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  workflow, or you don't need the data from the incomplete execution anymore, you can delete the incomplete exectution. To delete incomplete executions:
1
Go to the Incomplete executions tab.
2
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 .
3
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.
Errors that don't create incomplete executions
Most of the errors that can happen in  are connected with the flow of data in your scenario (like the DataError) or with the third party application (like the ConnectionError).
However, some errors don't create an incomplete execution:
When the error happens on the first module in the .
However, you can add the Break error handler ot the first module in the . With the Break error handler,  stores the incomplete execution even when the first module in the  outputs an error.
When your incomplete executions storage is full. If your incomplete executions storage is full,  checks the enable data loss﻿ setting:
If the data loss is disabled,  disables the scenario.
If the data loss is enabled,  keeps scheduling  runs and discards the incomplete execution if it cannot be stored in your account.
When the  runs longer than the  run duration limit. You can check the limit for your plan on the  pricing.
When an error happens during the initialization or rollback scenario phase﻿. Since these errors happen outside of the  operation phase, there is no incomplete  run.
Options related to incomplete executions
The following options in   settings determine if and how the incomplete executions are stored:
Allow storing incomplete executions
This option enables incomplete executions for the . If this option is disabled,  doesn't store incomplete executions of the .
Sequential processing
Sequential processing ensures that the  runs in a sequence. If there is an incomplete execution of the ,  pauses further scheduling of the  to keep the processing in the chronological sequence.  activates the  again after the  has no incomplete executions.

If the  has instant scheduling,  stores the arriving bundles in the webhook queue.
Enable data loss
Data loss setting controls what should happen when  cannot create an incomplete execution of a failed  run. This happens in most cases because the incomplete execution storage is full. Incomplete execution storage is limited based on the usage allowance.

If you keep data loss disabled,  pauses scheduling of the  to avoid losing any more  runs, until you clear the incomplete execution storage and enable the  again.

If you enable data loss,  will continue scheduling the  even if it couldn't store the incomplete execution.
﻿
Variables
Scenario execution, cycles, and phases