Make: ExecutionInterruptedError
Last verified
ExecutionInterruptedErrorWhat it means
Make outputs ExecutionInterruptedError when a scenario runs longer than the maximum execution time: 45 minutes on paid plans and 10 minutes on the Free plan, according to Make's documentation. Make treats it as a warning: the run ends, remaining bundles are not processed, and the scenario stays scheduled.
Because it is a warning, it will not deactivate the scenario, which makes it easy to miss. The symptom is usually that only part of a large dataset was processed.
What is not wrong: individual modules. Each step works; there are simply too many of them for one run.
What it looks like
Warning: ExecutionInterruptedError
Paid plans: 45 min per run Free plan: 10 min per runWhy it happens
- An iterator processes thousands of bundles through several modules in a single run.
- Slow modules (timeouts, retries, Sleep) accumulate across many bundles.
- Search modules return far more records than needed.
- The Free plan's shorter limit applies.
How to fix it
- Lower the Limit on search and trigger modules so each run processes a smaller batch.
- Split the scenario: one scenario collects work, another processes it in batches (for example via a data store or webhook).
- Batch API calls with aggregators and bulk endpoints instead of one call per bundle.
- Remove unnecessary Sleep modules or move them out of loops.
How to stop it recurring
Design for batches from the start: cap records per run, schedule more frequent smaller runs, and track progress in a data store so each run continues where the last stopped. Check History for warnings after any large import, since this warning leaves the scenario active and the only sign may be records that were never processed.
Official documentation: help.make.com/fix-errors-and-warnings. See all Make error messages or the Make limits and quotas.
Related errors
Definitions
- Make (formerly Integromat)Make (formerly Integromat) is a visual automation platform that connects apps and designs complex workflows us
- Error HandlingError handling is the practice of anticipating, detecting, and responding to errors in software execution, inc
- Rate LimitingRate limiting is a technique that controls the number of requests a client can make to a server within a given
- Retry LogicRetry logic is a fault-tolerance pattern that automatically re-attempts failed operations with configurable de
Quick answers
What does "ExecutionInterruptedError" mean in Make?
Make outputs ExecutionInterruptedError when a scenario runs longer than the maximum execution time: 45 minutes on paid plans and 10 minutes on the Free plan, according to Make's documentation. Make treats it as a warning: the run ends, remaining bundles are not processed, and the scenario stays scheduled. Because it is a warning, it will not deactivate the scenario, which makes it easy to miss.
How do I fix "ExecutionInterruptedError"?
1. Lower the Limit on search and trigger modules so each run processes a smaller batch. 2. Split the scenario: one scenario collects work, another processes it in batches (for example via a data store or webhook). 3. Batch API calls with aggregators and bulk endpoints instead of one call per bundle. 4. Remove unnecessary Sleep modules or move them out of loops.
Error handling you can see in the workflow
Autonoly workflows have per-node retries, timeouts, continue-on-fail and error-handler branches, so a failing step can be retried or routed instead of stopping the whole run. Saved workflows have no loop node; lists are worked through by the AI agent or one run per trigger item.
Also see Visual workflow builder.