Incomplete executionsSometimes Boost.space Integrator cannot successfully finalize a scenario execution due to an error. Boost.space Integrator stores incomplete executions in a folder named Incomplete Executions. Each stored incomplete execution can be resolved either manually or automatically. are a safety feature that protects your scenariosA specific connection between applications in which data can be transferred. Two types of scenarios: active/inactive. from stopping due to errors and from data lossThe data loss option enables data to be lost if Boost.space Integrator fails to save a bundle to the queue of incomplete executions (e.g. due to a lack of free space). Enable data loss to prevent interruptions in the overall scenario execution, e.g. a scenario where it is imperative the scenario keeps running and the incoming erroneous data is not... that could happen. When a scenarioA specific connection between applications in which data can be transferred. Two types of scenarios: active/inactive. encounters an error, with incomplete executions enabled, Boost.space IntegratorPart of the Boost.space system, where you can create your connections and automate your processes. stores the unfinished scenario run in the Incomplete executions tab.
![[Note]](https://docs.boost.space/wp-content/themes/bsdocs/docs-parser/HTML/css/image/note.png) |
Note |
|---|---|
| Incomplete executions are disabled by default. To store incomplete executions, enable the Allow storing incomplete executions option in the scenario settings. |
Make automatically retries specific incomplete executions:
- Incomplete executions caused by the
RateLimitErrorandConnectionError. - Incomplete executions created by the Break error handler, if you enable automatic completion of the incomplete executions.
If Make doesn’t retry an incomplete executionSometimes Boost.space Integrator cannot successfully finalize a scenario execution due to an error. Boost.space Integrator stores incomplete executions in a folder named Incomplete Executions. Each stored incomplete execution can be resolved either manually or automatically. automatically, you can fix the scenario and retry the scenario run manually.
|
Note |
|---|---|
| The maximum number of incomplete executions from all scenarios in all teams in an organization depends on your usage allowance.
If the limit is exceeded, you will get the following error:  |
To open the incomplete executions tab, select the scenario in the list of scenarios and switch from the DiagramThe diagram is a visual representation of your scenario and appears exactly the same way as you see your scenario in the Scenario editor. Use the diagram tab to quickly view:
the execution history of your scenario.
the number of operations and data consumed.
the controls to manage the scenario.
tab to the Incomplete executions tab.
In the scenario’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.
- Incomplete execution ID: A unique text generated by Boost.space Integrator 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 Boost.space Integrator created the incomplete execution.
- Size: The size of the incomplete execution blueprintBoost.space Integrator lets you import and export scenarios via a blueprint, a file in JSON format. Your blueprint contains all of your modules and settings except for connections. When importing from a blueprint, you must add your connections..
- 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 Boost.space Integrator will retry the incomplete execution.
- In progress: Boost.space Integrator is currently retrying the incomplete execution.
- Resolved: The incomplete execution has been resolved successfully. Boost.space Integrator will delete the resolved incomplete execution automatically after 30 days.
- Scheduled in: The approximate time until Boost.space Integrator will retry the incomplete execution.Before retrying, incomplete executions are put in a queue. The exact time when Boost.space Integrator will retry the incomplete executions might be different if you are retrying a lot of incomplete executions at the same time.
- Attempts: The number of attempts already made to resolve the incomplete execution.
- Detail: The Detail of the incomplete execution opens the scenario editor with the incomplete execution. In the incomplete execution detail, you can check the cause of the incomplete execution and resolve the incomplete execution.
Make checks the origin of every incomplete execution when they are created. Incomplete executions that have been created because of:
RateLimitErrorConnectionErrorModuleTimeoutError
are automatically retried by Make 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, Make marks the incomplete execution as Resolved and stops retrying.
If all of the retry attempts fail, Make 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. Make doesn’t retry these error types automatically by default.
In addition, Make 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.
When dealing with scenario incomplete executions, you should first decide if you want to finish the run and process the rest of the data in the scenario. If you want to finish the scenario 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 editor opens.
- 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 execution. Retrying an incomplete execution is like another attempt to run a scenario. The incomplete execution runs with the same module settings as when the error happened.
|
Note |
|---|---|
| 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.
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 is active. You can retry incomplete executions only when the scenario is active.To activate a scenario, go back to the Diagram tab or the scenario editor and click the switch next to scenario schedulingBoost.space Integrator allows you to define when and how often an active scenario runs. Use the Schedule setting panel under the Options tab and choose Scheduling to set your preferred schedule. on the scenario 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.
- 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 Make starts retrying them.
Note 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 Boost.space Integrator 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.
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 run history, or from the incomplete executions tab:
You might want to check the scenario 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. Boost.space Integrator 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, Boost.space Integrator 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, Boost.space Integrator creates a new incomplete execution, starting with the module that caused the new error.
When you don’t need to finish the scenario 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.
- Click the button Delete selected to delete the incomplete executions.
The deleted incomplete executions are no longer in the list of incomplete executions.
![[Warning]](https://docs.boost.space/wp-content/themes/bsdocs/docs-parser/HTML/css/image/warning.png) |
Warning |
|---|---|
| Once you delete an incomplete execution, it cannot be put back. |
Most of the errors that can happen in Make 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 scenario.However, you can add the Break error handler to the first module in the scenario. With the Break error handler, Boost.space Integrator stores the incomplete execution even when the first module in the scenario outputs an error.
- When your incomplete executions storage is full. If your incomplete executions storage is full, Boost.space Integrator checks the enable data loss setting:
- If the data loss is disabled, Boost.space Integrator disables the scenario.
- If the data loss is enabled, Boost.space Integrator keeps scheduling scenario runs and discards the incomplete execution if it cannot be stored in your account.
- When an error happens during the initialization or rollback scenario phase. Since these errors happen outside of the scenario operationOperations are tasks in integration scenarios, similar to "operations" in Make.com. Each action, like reading or updating a record, counts as one operation. They’re essential for data syncing between apps and reset monthly. Going over the limit pauses syncing until you add more or upgrade your plan. phase, there is no incomplete scenario run.
The following options in Boost.space Integrator scenario settings determine if and how the incomplete executions are stored:
- Allow storing incomplete executionsThis option enables incomplete executions for the scenario. If this option is disabled, Make doesn’t store incomplete executions of the scenario.
- Sequential processingUsing the Sequential processing options allows you to monitor and resolve errors in greater detail. If you enable sequential processing, Boost.space Integrator stops processing the task sequence until you resolve all incomplete executions. With sequential processing enabled, you can address all incomplete executions in the order in which they occurred. If you disable Sequential processing, the scenario continues to run...Sequential processing ensures that the scenario runs in a sequence. If there is an incomplete execution of the scenario, Make pauses further scheduling of the scenario to keep the processing in the chronological sequence. Make activates the scenario again after the scenario has no incomplete executions.
If the scenario has instant scheduling Make stores the arriving bundles in the webhookA webhook is a way for an app to send real-time information to a specific URL in response to certain events or triggers. queue.
- Enable data lossData loss setting controls what should happen when Make cannot create an incomplete execution of a failed scenario 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, Make pauses scheduling of the scenario to avoid losing any more scenario runs, until you clear the incomplete execution storage and enable the scenario again.
If you enable data loss, Make will continue scheduling the scenario even if it couldn’t store the incomplete execution.