Skip to main content

Celonis Product Documentation

Incomplete executions

Incomplete executions is a folder where Action Flow executions that could not be successfully finalized due to an error are stored. Each stored incomplete execution can be resolved either manually or automatically.


By default the storing of incomplete executions is disabled. To enable it, enable the Allow storing incomplete executions option in the Action Flow advanced settings.

If a module encounters an error during its operation (see the Errors resulting in incomplete executions), a new incomplete execution is added to the Incomplete executions folder. Each incomplete execution contains the Action Flows blueprint and all the bundles that can be mapped into the failed module. You can see the list of incomplete executions in the Incomplete executions tab.



The size limit of the unresolved incomplete executions folder per organization depends on the number of operations in your pricing plan.

If the limit is exceeded, you will get the following error:

Resolving incomplete executions

When a new incomplete execution is stored, you can resolve it as follows:

  1. Go to the Incomplete executions tab.

  2. Go to the exact incomplete execution.

    • If you want to see the log of all module's operations first:

      1. Go to the History tab.

      2. Locate the failed execution log and click Details.

      3. Click the failing module that has an error.

      4. Click Resolve. Celonis platform redirects you to the very incomplete execution.

    • If you want to directly go to the incomplete execution:

      1. Go to the Incomplete executions tab.

      2. Locate the failed execution and click Details.

  3. Click the failing module. A scenario canvas opens.

  4. Check the module settings and fix the reason for the error.

  5. Click Save.

  6. Click Run once.

Options related to incomplete executions

The following options in Celonis platform Action Flow settings determine if and how the incomplete executions are stored:

  • Allow storing incomplete executions

  • Sequential processing

  • Enable data loss

Errors resulting into incomplete executions

There are several categories of errors that result into storing of incomplete executions. These may include: validation errors arising from incomplete or erroneous data, mostly because of a missing item that is expected in order to successfully process all data going through a module; or errors occurring from the final destination's unavailability because of temporary or long term connection failure (e.g. during connection to email or remote FTP server).

  1. If an error occurs on the first module in the Action Flow, the execution stops immediately and no incomplete execution is stored.

  2. If an error occurs on any other module and there is no error handler route attached, then:

    • If the error type is ConnectionError, RateLimitError, OutOfSpaceError or ModuleTimeoutError, an incomplete execution record WITH auto-retry is stored.

    • If the error type is DataError, InvalidConfigurationError, InvalidAccessTokenError, UnexpectedError, MaxFileSizeExceededError or MaxResultsExceededError, an incomplete execution record WITHOUT auto-retry is stored.

    • If the error type is anything other than the above, the execution fails.