Make error handlers, how do I set them up correctly?
Make has per-step error handler routes where you decide what to do on failure: Resume, Rollback, Commit, Break, or Ignore. The default is usually wrong for production.
Try this first
- 1Resume: continue the flow as if nothing happened. Fits 'best-effort' steps (a notification that may miss).
- 2Rollback: undo work done in this run and stop. Fits 'all-or-nothing' transactional flows.
- 3Commit: stop with success status, as if the step went well. Almost always wrong, hides failures.
- 4Break: write an 'incomplete execution' record and stop, you can re-submit manually later. Good for flows with a dead-letter flow.
- 5Ignore: skip this step, continue to the next. Fits when the error is an undesired but acceptable deviation.
When to bring us in
Got Make scenarios with default error handling and silent failures, a review of error routes usually fixes it. We can look.
See also
- n8n: self-host or cloud?Self-hosted is cheaper at volume and keeps data local. Cloud removes ops burden.
- Zapier or Make: which fits better?Zapier is straight-line; Make handles complex flows with routers and iterators for less money.
- Power Automate Cloud or Desktop: which to use?Cloud for SaaS integrations and triggers. Desktop for RPA against legacy Windows apps without APIs.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.