Lorixen.
EN

Make Scenario Errors: Incomplete Executions, Retries and Error Handlers

Short answer: In Make, a module that errors normally stops the run, and if it keeps happening the scenario can be switched off automatically. To make failures recoverable, enable Allow storing of incomplete executions in the scenario settings, then attach an error handler route to each risky module and choose a directive: Break to store the run and retry it later, Resume to continue with substitute data, Ignore to skip the item, or Rollback and Commit to stop the run on purpose. Think about which steps already ran before the failure, so retries do not create duplicate records, and send yourself an alert whenever a handler fires.

Scenario settings to check first

Open the scenario, click the gear icon for Scenario settings, and review these options described in Make's scenario settings documentation:

  • Allow storing of incomplete executions. When on, a run that fails in a way your error handling routes to Break (or in some cases by default) is saved with its data, so you can fix the problem and resume it rather than lose the item.
  • Number of consecutive errors. After this many failed runs in a row, Make deactivates the scenario. That protects your operations quota but can quietly stop a lead pipeline. Know what the value is and make sure someone is alerted when it trips.
  • Sequential processing. Forces incoming items, such as webhook calls, to be processed one at a time in order. Useful when later items depend on earlier ones, and necessary if incomplete executions must be resolved before new runs proceed.

Saved incomplete executions appear on the scenario's Incomplete executions tab. Make's incomplete executions page explains how to inspect, resolve or delete them.

The five directives in plain language

Right-click a module and choose Add error handler to attach a route that runs only when that module fails. The handler ends in a directive:

Directive What happens to this item Run status Typical use
Break Stops, stored as an incomplete execution, can retry automatically Warning Temporary API failures, rate limits
Resume Continues with values you supply Success Optional data, a fallback default
Ignore Skips the rest for this item, moves to the next Success Non-critical step, such as a Slack ping
Rollback Stops the run, reverts what can be reverted Error All-or-nothing steps with supporting modules
Commit Stops the run, keeps what has been done Success Stop processing cleanly after partial work

Break has an option to complete the execution automatically, with a number of attempts and an interval between them. For flaky APIs this is the closest thing Make has to a built-in retry.

A worked example: a web shop order

Picture this scenario for a small online shop:

  1. Webhook receives a new order from the shop.
  2. Google Sheets adds a row to the order log.
  3. Invoicing app creates an invoice.
  4. Email sends the invoice to the customer.
  5. Slack posts "New order" in the team channel.

Now the invoicing app returns a 503 error at step 3. Without error handling, the run stops: the order is in the sheet, but no invoice exists and no email goes out. Nobody notices until the customer asks.

A better setup:

  • Step 3 gets a Break handler with automatic completion, for example three attempts a few minutes apart. When the invoicing app recovers, Make continues from step 3 and the customer gets their invoice.
  • Step 5 gets an Ignore handler. If Slack is down, the order should still complete.
  • Step 4 gets a Break handler too, so a mail outage does not lose the invoice email.

Partial runs and duplicate records

The trap with retries is duplicates. In the example, step 2 already wrote a sheet row before step 3 failed. If you rerun the whole scenario manually from the webhook, you get a second row.

Ways to stay clean:

  • Resume incomplete executions instead of rerunning from scratch. Resuming continues from the failed module, so earlier steps do not repeat.
  • Search before create. Before creating an invoice or contact, add a search module for an existing record with the same order ID and use a router or filter to skip creation if found.
  • Use unique keys. Store the order number in every system you write to, so duplicates are easy to spot and many apps reject them.
  • Order the steps carefully. Put the step most likely to fail early, before steps that are hard to undo.

Getting notified before customers notice

Make sends email notifications for errors and deactivations, depending on your notification preferences in your profile. Do not rely on one inbox:

  • Add an error handler route that sends a message to a team channel or email with the scenario name, module name, error message and the order ID, then ends with Break so the item is still stored.
  • Use a dedicated alerts address that more than one person reads.
  • For critical scenarios, set a daily summary check: a separate small scenario that counts incomplete executions and alerts you if the number is above zero.

A weekly review of failures

Spend ten minutes each week on each important scenario:

  • [ ] Open History and filter for warnings and errors
  • [ ] Check the Incomplete executions tab and resolve or delete each item
  • [ ] Look for repeating error messages, which point to a lasting cause such as expired credentials
  • [ ] Reconnect any connection showing an authorization error
  • [ ] Note operations used by retries, since repeated attempts count toward your plan's usage
  • [ ] Confirm the scenario is still active

Write recurring causes in a short log. If the same API fails every Monday morning, a schedule change or a delay module may solve it better than more retries.

FAQ

Why did Make turn my scenario off?

It hit the consecutive errors limit in scenario settings. Fix the cause, then reactivate. Handled errors routed through Break or Ignore do not count the same way as unhandled ones, so error handlers make deactivation less likely.

Are incomplete executions kept forever?

No. They are stored for a limited time and your plan's storage limits apply. Check Make's help pages for the current rules and resolve them promptly.

Does Rollback undo a Google Sheets row?

Only modules that support transactions can be rolled back, and most third-party app modules do not. Treat Rollback as "stop now with error status" unless you know the modules involved support it.

If a scenario keeps failing in ways these settings do not catch, send us its outline and we will help design error paths that hold up.

Sources

WhatsAppBook a call