Make Scenario Stopped Running? 5 Ways to Fix It Now

6:14pm on a Friday in November. Priya had her laptop bag half-zipped when the Slack came in. It was the client’s COO: “We haven’t had a single lead since Tuesday. Did something break?”

She runs 40 client workflows across her agency. This Make.com scenario was the one she worried about least, which is its own kind of warning sign. It routes about 1,200 leads a month. Her best client. She opened her account expecting a wall of red error flags, the loud kind of broken she knew how to fix.

There were none. The scenario just sat there. Toggle flipped to “Off.” No alarm, no email, no execution history for three days. Three days of qualified leads gone, while she had spent the week telling herself everything was fine because nothing had screamed otherwise.

The turn came when she actually looked at the toggle instead of the error log. Off. Not crashed. Off. Somebody, probably her, had opened a module to tweak it days earlier, saved, and the save had quietly left the whole thing deactivated. That was the entire failure. A switch in the off position, invisible because she had been watching the wrong part of the screen.

If you are staring at a frozen Make screen right now, here is the order that gets you back fastest. Start with the toggle. Then the five reasons it flips off without telling you.

Start with the toggle, because half the time that is the whole story

The fastest fix has nothing to do with broken APIs or routing logic. The scenario just is not turned on.

Make puts an ON/OFF toggle in the top right of the scenario builder. Clicking save does not flip it back on. Edit a module, save, walk away, and the scenario sits off until you notice. Which can be three days.

Look at it now. If it reads “Off” and the execution history is empty with no red bubbles, flip it on, hit “Run Once” to clear the backlog, and you are running again. If it keeps switching itself off, the checks below explain why. This same shape of failure shows up everywhere, not just Make. The cross-tool version is in My Automation Broke and I Don’t Know Why, Automation Stopped Working But Shows No Error, and How to Prevent Silent Automation Failures.

Why a scenario flips itself off

“All my scenarios stop running automatically on their time schedule, if I want to run a scenario I have to manually click ‘Run Once’.”

— Sam_Krausz on Make Community, 2024-02-29

That is Priya’s exact symptom, posted by a stranger a year earlier. Five things cause it.

Auto-paused after repeated errors. Toggle off, and the history shows a run of failures right before the silence. Make protects itself and your connected services by killing a scenario that keeps failing. Three consecutive errors by default, then it flips the switch for you and says nothing. Open the gear icon at the bottom of the builder, find “Scenario settings,” and check the “Sequential Errors” rule to confirm.

The schedule trigger went inactive. You can hit “Run Once” and it works, but it refuses to run on its own. Click the clock icon on your first trigger module. The scheduling inputs got cleared, or point at a date in the past, and a schedule with no valid time to fire just sleeps forever.

You hit the operations cap. The scenario reads “On” but has processed nothing since the 15th. Open your organization account and look at the monthly operations usage. Past the cap, Make halts every execution across the whole account until the billing cycle resets or you buy more operations. Nothing breaks. Everything just stops.

“The scenario I built was working fine and there were no issues or error messages from make.com. Then all of the sudden when I am testing my voice agent… it says that it can’t find the availability.”

— Marcus_Perkovic on Make Community, 2025-05-03

A connected app dropped the login. The scenario triggers, then dies on a Google, Salesforce, or Microsoft module with an authentication error. Open the “Connections” tab and look for a warning triangle. Expired credentials are far more common than people expect. Here is the difference that matters: a useless alert reads Error [401]: Invalid credentials for module 14, and a useful one reads Your Salesforce connection expired in the Lead Routing scenario. Reauthorize here. Same failure. One you can act on, one you have to decode. Reauthorize directly in the connections tab.

A timezone mismatch made it look skipped. Your daily summary fires at 3am instead of 8am, or seems to miss whole days. Make defaults to UTC for a lot of its internal scheduling. Schedule a 5pm run in your head while the scenario reads it as UTC, and it runs hours off from when you expect, which looks identical to never running at all. Check your account timezone in profile settings, then the scenario’s advanced scheduling.

What Priya changed after that Friday

Fixing the token or the error threshold gets you running again today. None of it answers the question Priya could not stop turning over that night: the scenario was off for three days and the first thing to tell her was a client. Not the tool. Not an email. A client, on a Friday evening, asking if something broke.

So she stopped trying to watch 40 toggles by hand. NoCrash watches her scenarios from the outside and messages her in plain language the moment one goes quiet or a schedule stops firing, before the client opens Slack. Connect your first scenario free at nocrash.io and the next time a toggle flips, you hear it from us. None of this is hard. It’s just nobody’s job until it’s everybody’s emergency. Make it somebody’s job before then.