Skip to content

Incomplete executions

Incomplete executions is a folder where scenario 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 scenario 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 scenarios blueprint and all the bundles that can be mapped into the failed module. The list of incomplete executions can be opened by clicking on the INCOMPLETE EXECUTIONS tab on the scenario detail page:



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


See also the Enable data loss scenario setting.

Resolving incomplete executions

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


  2. Locate the incomplete execution you would like to resolve and click Detail.


If you first wish to see the log of all module's operations before you attempt to resolve the incomplete execution, you may resolve the incomplete execution from the HISTORY folder:

  1. Click the HISTORY tab.

  2. Locate the scenario failed execution log and click Details.


  3. Open the module's log where all the module's operations are shown.

  4. Locate the failed operation and click Resolve:


The following options in scenario 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 scenario, 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.

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