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.
If a module encounters an error during its operation (see the Errors resulting into incomplete executions), a new incomplete execution is added to the Incomplete executions folder. Each incomplete execution contains the scenario's 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 in the scenario detail page:
When a new incomplete execution is stored, you can resolve it as follows:
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:
The following options in the Scenario settings panel determine if and how the incomplete executions are stored:
There are several categories of errors which 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).