Examine 5 Error Handler Directives When Make Scenarios Fail

Right-clicking any module and selecting Add error handler opens an orange fallback route triggered exclusively on failure. Terminating this route with one of Make's five official directives dictates exactly how the failed bundle is treated. Here is how each directive manages data flow according to official specifications.

Which Directive Should You Choose When a Module Errors Out?

While normal executions follow a single forward line, error handlers branch the journey at the exact moment of failure.

Input Arrival → Standard Module Processing → [On Error] → Error Handler Route → Directive Execution

Your choice of directive determines whether the failed bundle is discarded, padded with fallback values, or held in a retry queue. The following table contrasts the five directives.

This comparison reflects official Make documentation verified on October 26, 2026.

How Do Resume and Ignore Differ in Data Flow?

Both directives allow the scenario to continue processing downstream modules after a failure, yet they produce fundamentally different output payloads.

Resume allows you to inject substitute data (a fallback bundle) in place of the failed module's output. For example, if a CRM lookup module fails with a temporary 404, but a subsequent email module strictly requires a customer_name variable, you can define customer_name: "Valued Customer" in the Resume directive. The email module then executes cleanly without throwing secondary missing-variable errors.

Ignore, by contrast, provides no replacement data and passes an empty output forward. If downstream modules depend on fields that were supposed to be generated by the failed module, they will fail immediately. Therefore, reserve Ignore strictly for non-critical notification or logging modules whose outputs are never referenced downstream.

How Do Commit and Rollback Handle Transactions and Downstream Nodes?

Workflows that interact with databases, payment gateways, or ERP systems must carefully manage state when an intermediate step fails.

Commit finalizes and saves all operations completed up to the point of failure, stopping that branch immediately while marking the scenario run as Success. For instance, if lead enrichment fails due to an invalid phone number, but you want to preserve the newly registered contact record without triggering subsequent alert emails, Commit stops the run cleanly without raising error alarms.

Rollback operates in the opposite direction. It halts scenario execution and reverts preceding operations associated with the current bundle. However, rollback works exclusively on relational database modules (such as MySQL or PostgreSQL) that support ACID transactions. Standard SaaS APIs (like posting to Slack or appending rows to Google Sheets) do not support transactional rollbacks, so partial writes across those services cannot be undone automatically.

When Should You Use the Break Directive and the Incomplete Executions Queue?

In production environments, Break is the most resilient directive for weathering external service instability, network timeouts, and HTTP 429 rate limits.

When Break executes, the failed bundle immediately moves into Make's Incomplete Executions queue. You can configure up to 5 automated retry attempts with custom intervals (such as 5-minute backoffs). As soon as the external service recovers, Make resumes processing the bundle starting from the failed module, seamlessly completing the rest of the workflow.

If the issue persists through all scheduled retry attempts, the bundle does not disappear. Instead, it enters a Waiting for review status within the queue. System administrators can later fix the root cause and click Resolve in the Make dashboard to re-execute the bundle manually, preventing data loss in critical order or billing workflows.

What Should You Verify Before Adding Error Handlers to Production?

Before deploying error handler routes to production scenarios, administrators should audit three critical configuration points:

1. Enable Incomplete Executions in scenario settings: Ensure Allow storing incomplete executions is toggled on in the scenario settings. If this toggle is off, Break directives cannot store bundles and the scenario terminates as a standard failure.
2. Audit downstream variable dependencies: Verify whether subsequent nodes rely on outputs from the failed module. If required fields exist, use Resume with structured defaults rather than Ignore.
3. Decide batch isolation policies: When processing multiple bundles in a loop, decide whether one bundle's failure should abort the entire scenario (Rollback) or isolate the failure while continuing remaining bundles (Break or Ignore).

For configuring webhooks and signed retries in Make, review /safe-ops/make-event-subscriptions-signed-retries/. To compare how n8n structures execution retries and error triggers, explore /safe-ops/n8n-failed-execution-retry-workflow-choice/.

Before launching new directives in live workflows, test them by feeding intentionally invalid credentials or malformed payloads to verify that bundles branch exactly as planned.