Try or ByeTry or Bye

Make ExecutionInterruptedError (Scenario Timeout)

Workaround available Web Updated October 21, 2026

Quick answer

ExecutionInterruptedError means the run exceeded Make's maximum execution time: 40 minutes on paid plans, 5 minutes on Free. Remaining bundles aren't processed. Split the job into smaller chained scenarios and lower search limits.

Most likely fix: Split into chained scenarios.

Symptoms

A warning shows ExecutionInterruptedError on one of the last modules; long syncs only process part of the data.

Why it happens

  • Run longer than 40 minutes (5 minutes on Free)
  • Search modules returning thousands of items
  • Slow external APIs or Sleep modules adding time

How to fix it

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

  1. 1. Split into chained scenarios

    1. Move the second half of the work into a new scenario with a Custom webhook trigger
    2. From the first scenario, send items to that webhook with the HTTP module
    3. Each scenario then gets its own time limit

  2. 2. Lower the per-run limit

    1. Open the trigger or search module
    2. Reduce 'Limit' / 'Maximum number of results'
    3. Run the scenario more often to cover the volume

  3. 3. Store incomplete executions

    1. Open Scenario settings
    2. Enable 'Allow storing of incomplete executions' to review and resume interrupted runs (behavior on Free may differ)

  4. 4. Batch API calls

    1. Use bulk modules or aggregators to reduce the number of calls per run

This guide also covers

  • make executioninterruptederror
  • make scenario timeout
  • make 40 minute limit
  • make execution time limit

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