Scenarios execution degraded

What to do

• Check whether you use Make eu1.make.com, eu2.make.com, us1.make.com, us2.make.com and 3 more. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1d 4h it lasted.

  Anything that failed between 2026-07-30 07:55 UTC and 2026-07-31 12:35 UTC may need a replay.

• Subscribe to Make's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=make works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Make 4

1. investigatingJul 30, 2026, 7:55 AM UTC

   We are currently investigating a minor incident affecting approximately 250 scenarios to fail. Impact appears limited, and our team is actively working to confirm the full scope and root cause. We will provide an update as soon as more information is available.

   provider

2. investigatingJul 30, 2026, 8:54 AM UTC

   Our engineers are continuing to investigate this issue with highest priority. We will provide a further update within the next hour.

   provider

3. identifiedJul 30, 2026, 9:41 AM UTC

   We have identified the cause of the scenario execution failures affecting approximately 250 scenarios. Our team is currently re-enabling any scenarios that were disabled as a result, and is working on a fix to prevent this issue from reoccurring. We will provide a further update once the fix has been applied.

   provider

4. resolvedJul 31, 2026, 12:35 PM UTC

   We’re reaching out to let you know that the issue affecting scenario execution has been resolved, and most of the previously disabled scenarios have been re-enabled. Remaining affected scenarios will be handled individually. System execution has stabilized and normal operations have resumed.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.