Incomplete executions
Incomplete executions are a safety feature that protects your Action Flows from stopping due to errors and from data loss that could happen. When a Action Flow encounters an error, with incomplete executions enabled, Celonis platform stores the unfinished Action Flow run in the Incomplete executions tab.
Note
Incomplete executions are disabled by default. To store incomplete executions, enable the Allow storing incomplete executions option in the Action Flow settings.
To open the incomplete executions tab, select the Action Flow in the list of Action Flows and switch from the Overview tab to the Incomplete executions tab.
In the 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 Action Flow.
Incomplete execution ID: A unique text generated by Celonis platform to identify the incomplete execution.
Created: The date and time when Celonis platform 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 Celonis platform will retry the incomplete execution.
In progress: Celonis platform is currently retrying the incomplete execution.
Resolved: The incomplete execution has been resolved successfully. Celonis platform will delete the resolved incomplete execution automatically after 30 days.
Scheduled in: The approximate time until Celonis platform will retry the incomplete execution.
Before retrying, incomplete executions are put in a queue. The exact time when Celonis platform 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 Action Flow editor with the incomplete execution. In the incomplete execution detail, you can check the cause of the incomplete execution and resolve the incomplete execution.
We check the origin of every incomplete execution when they are created. Incomplete executions that have been created because of:
RateLimitErrorConnectionErrorModuleTimeoutError
If a retry attempt succeeds, Celonis Platform marks the incomplete execution as Resolved and stops retrying.
If all of the retry attempts fail, Celonis Platform 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. Celonis Platform doesn't retry these error types automatically by default.
In addition, Celonis Platform automatically retries incomplete executions created with the brek error handlerwith the automatic run completion enabled. The number of retries and the delays between them depend on the Break error handler settings.
When dealing with Action Flow incomplete executions, you should first decide if you want to finish the run and process the rest of the data in Action Flow. If you want to finish the Action Flow 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 Action Flow editor opens.
Click the warning sign on the module that caused the error.
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 Action Flow. The incomplete execution runs with the same module settings as when the error happened.
If the error requires changes in the module settings or in the general Action Flow blueprint, you need to resolve the incomplete execution manually.
If you find out that you don't need to run the rest of the Action Flow, you can delete the incomplete execution.
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 Action Flow run history, or from the incomplete executions tab:
You might want to check the Action Flow 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. Celonis platform 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, Celonis platform 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, Celonis platform 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 Action Flow workflow, or you don't need the data from the incomplete execution anymore, you can delete the incomplete execution. 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 Action Flow.
Click the button Delete selected to delete the incomplete executions.
The deleted incomplete executions are no longer in the list of incomplete executions.
Warning
Once you delete an incomplete execution, it cannot be put back.