Errors that don't create incomplete executions

most of the errors that can happen in {{product name}} 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 {{scenario singular lowercase}} however, you can add the break error handler ot the first module in the {{scenario singular lowercase}} with the break error handler, {{product name}} stores the incomplete execution even when the first module in the {{scenario singular lowercase}} outputs an error when your incomplete executions storage is full if your incomplete executions storage is full, {{product name}} checks the overview of error handling docid 7 hehdtuu2xyys8 qurub setting if the data loss is disabled, {{product name}} disables the scenario if the data loss is enabled, {{product name}} keeps scheduling {{scenario singular lowercase}} runs and discards the incomplete execution if it cannot be stored in your account when the {{scenario singular lowercase}} runs longer than the {{scenario singular lowercase}} run duration limit you can check the limit for your plan on the {{product name}} pricing when an error happens during the initialization or rollback scenario execution, cycles, and phases docid\ m3kmlkl8455cs zz13ytb since these errors happen outside of the {{scenario singular lowercase}} operation phase, there is no incomplete {{scenario singular lowercase}} run