A failing module can stop everything behind it
Make's default, with no error handling and incomplete executions off, is to roll back: stop the run, revert changes where modules support it and end with an error status. After repeated failing runs, three in a row by default, the scenario is deactivated, and one triggered by a webhook is disabled at once. A single malformed record can therefore halt a whole schedule and then switch it off. Nothing in that behaviour tells a person unless an alert has been added.
Error routes, handlers and stored records
Make lets you attach an error route to a module with one of five handlers: skip, retry, resume, commit or rollback. Turning on Store incomplete executions keeps a failed run so it can be fixed and resumed, and Make says errors then become warnings. The trade-off is that, as Make documents, when an error creates a stored incomplete execution the next scenario run is postponed until that record is resolved or the Retry handler resolves it. A held record therefore needs an alert and an owner. A route that only sends a message and has no handler ends with Make skipping the error, so add the directive you mean. Choose the handler by what losing a record, or pausing later runs, would cost.
Whose clock, and what Make cannot fix
Scheduled scenarios run in the organisation's time zone, set by an owner or admin; a user's time zone only changes how times are displayed. An error route does not repair a lost connection or an exhausted plan, which need the account holder. If a scenario depends on an API that must not miss or repeat records, the job is also about checkpoints and keys, which the polling guide explains.
Choose the outcome that matches the symptom
A scenario halts on one record and later records wait: the outcome for one scenario and one failing module adds an error route with a directive you choose, an alert, and tests on a copy with a deliberately bad record and a second run. Nobody is told when scenarios fail: the failure-alerts outcome covers up to five named automations. Scenarios fail now and then and nobody watches: the standing monitor-and-repair service. We work on copies fed by disposable data, you switch changes on, and no outcome promises round-the-clock cover or a response time.
Sources and limits
- Make: overview of error handling Checked 2026-10-11.
- Rollback is the default when no handler is set and incomplete executions are off; a scenario is deactivated after the configured consecutive errors, three by default, and a webhook-triggered scenario is disabled immediately.
- An error route does not have to contain a handler, and if no module outputs an error in it Make skips the error; the Skip handler marks the run as successful.
- When an error creates an incomplete execution, Make postpones the next scenario run until it is resolved or the Retry handler resolves it automatically.
- Make: incomplete executions Checked 2026-10-11.
- Incomplete executions are off by default and enabled with Store incomplete executions.
- Make: manage time zones Checked 2026-10-11.
- Scheduled scenarios run in the organization's time zone, and the user time zone only changes display.