Live / Make / Incident
Make: Failing scenarios with "Scenario" app
Make · make.comMinor incidentResolved2026-10-12 09:29 UTC
Public — what happened
Summary
Make reported a minor problem on October 12, 2026, starting at 08:23 UTC, in which automations that rely on its built-in "Scenario" app, such as modules that start or run another scenario or return output, failed with a validation error as soon as they began running. By 08:36 UTC the company said it had found the problem and was working on a fix, though it did not describe the cause. Make noted that some affected scenarios might have been switched off and said it would turn them back on. The incident was marked resolved at 09:29.
Affected
eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com
Timeline
- Started — 2026-10-12 08:23 UTC
- Investigating — 2026-10-12 08:23 UTC
- Identified — 2026-10-12 08:36 UTC
- Resolved — 2026-10-12 09:29 UTC · 1h 06m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Make against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Make: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Make report →
More from Make
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.