A global scenario resilience setting in Make that prevents scenario deactivation on execution errors while queuing failed runs for retry and sending error digests, eliminating per-module error handler overhead.
Built for Enterprise and mid-market Make users running mission-critical automation workflows who need fault tolerance without complex error handling logic in every module..
The receipts — real demand
“I understand that on a scenario I can add error handling with every app, but is there any way to keep a scenario running (processing new executions) without doing that? As in ideally there is some global ‘don’t deactivate this scenario when it errors, keep processing new executions and email me to let me know of the one execution that failed’. Does such a setting exist?”
🔁 Corroborated on other sources
“Would be great if we can run a scenario when entire scenario fails. Internal scenario error handling stay as is. This way we can push errors into observability system(s) (Sentry, DataDog, etc). This feature is especial…”
view →“If I understand correctly, you are wanting the zap to follow in an ordered process such as A->B->C, but stop before C if nothing needs to be done? If this is the cause this is not possible. When your zap counts it as a success, it is really referring to your automation that…”
view →“Also, transitioning from one Zap to another is messy — there’s no way to “drain” delayed runs without fully turning off the Zap, which effectively kills all in-progress actions.I can’t imagine I’m the only one who has struggled with this ... Does Zapier Path Steps allows to run m…”
view →“Hi Everyone, is there a way to stop a scenario execution on purpose? I know the error handling modules (commit, ignore…) but in my case it’s not an error. The marked “Search Rows” modules has 10 collections and in most cases I only need three (or 4,5,6…). This is the case when I …”
view →Why this is a gap
This pain showed up independently across 3 different sources — the strongest signal that demand is real and underserved.