---
title: Errors that don't create incomplete executions
slug: errors-that-dont-create-incomplete-executions
docTags: 
createdAt: 2025-04-08T11:52:13.839Z
---

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