Try or ByeTry or Bye

Make Scenario Turned Off Automatically

Workaround available Web Updated October 21, 2026

Quick answer

Make disables a scenario's schedule after errors across several consecutive runs, and immediately on fatal errors like DataSizeLimitExceededError. Outages have also auto-disabled scenarios. Find the failing module in History, fix it, then switch the scenario back on.

Most likely fix: Find the failing module.

Symptoms

Scenario toggle is OFF without anyone changing it; email notice that the scenario was deactivated; automations silently stopped.

Why it happens

  • Consecutive errors on scheduled runs (warnings don't count)
  • Instant (webhook) scenarios stopping on the first error
  • Fatal errors such as exceeding data transfer limits
  • Connections failing after all reconnect attempts
  • Make platform incidents that disable scenarios

How to fix it

Try these in order — the most common fix is first.

  1. 1. Find the failing module

    1. Open the scenario and go to History
    2. Open the latest failed run
    3. Click the module with the red warning to read the error

  2. 2. Add error handling

    1. Right-click the failing module and choose 'Add error handler'
    2. Use Resume or Skip (formerly Ignore) for expected failures, Break to retry later
    3. Enable 'Allow storing of incomplete executions' in scenario settings

  3. 3. Adjust the consecutive-errors setting

    1. Open Scenario settings
    2. Set 'Number of consecutive errors' to a value that fits your tolerance
    3. Keep it low if failures would waste credits

  4. 4. Check status and re-enable

    1. Check status.make.com for incidents
    2. Fix the cause, then turn the scenario toggle back ON

This guide also covers

  • make scenario turned off
  • make scenario deactivated
  • make scenario stopped running
  • make disabled scenario

Still not working?

If Make keeps failing, you're not alone. See every Make problem users report or the alternatives people switch to.

Other Make errors