Errors that don't create incomplete executions

1min

Most of the errors that can happen in  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 .
However, you can add the Break error handler ot the first module in the . With the Break error handler,  stores the incomplete execution even when the first module in the  outputs an error.
When your incomplete executions storage is full. If your incomplete executions storage is full,  checks the enable data loss﻿ setting:
If the data loss is disabled,  disables the scenario.
If the data loss is enabled,  keeps scheduling  runs and discards the incomplete execution if it cannot be stored in your account.
When the  runs longer than the  run duration limit. You can check the limit for your plan on the  pricing.
When an error happens during the initialization or rollback scenario phase﻿. Since these errors happen outside of the  operation phase, there is no incomplete  run.
﻿

Manage incomplete executions