Context: Web, official Make skills repo (github.com/integromat/make-skills, error-handling.md): Make has five error handlers, each attached to an individual module (not the scenario). Break stores an incomplete execution for later retry; Commit stops but keeps partial work; Ignore skips the failed bundle and continues; Resume substitutes a fallback mapping; Rollback stops and reverts transactional (ACID) m

[official Make skills repo, real gotcha]: a Make scenario with no error handlers dies on the first module error, and consecutive failing runs get the scenario's scheduling disabled. The fix is per-module error handlers (right-click the module -> Add error handler):

- Break: parks the run as an incomplete execution; set auto-retry to get Retry behavior, or resolve it manually later. Use for ConnectionError and RateLimitError.
- Commit: stops the run, marks it success, keeps changes made so far.
- Ignore: drops the failed bundle, keeps processing the rest. Use for non-critical modules.
- Resume: feeds a fallback mapping into downstream modules so the flow continues. Use for DataError where a default makes sense.
- Rollback: stops everything and reverts ACID-labeled modules. Only works on transactional modules (database apps, data stores); Gmail sends and file deletes cannot be undone.

No handler helps InvalidConfigurationError: that one you fix in the module config.