// AUTOMATION FIXES
Make scenario stopped running? Get it back without losing the data
A Make scenario stopped running usually means Make switched it off after an error, a connection needs reauthorising, or the webhook feeding it went quiet. Make deactivates a scenario with an instant trigger the moment one run errors. Web Blend builds and runs Make.com, n8n and Zapier automations for trade and service businesses, and is a ServiceM8 Bronze Partner. We turn it back on without losing what’s queued, then watch for silence so the next stop is caught early.
Updated October 2026. Make behaviour checked against Make’s help centre and Make Academy on 30 October 2026.
// CHECK IT NOW
Six checks before you touch anything
Don’t delete or rebuild the scenario yet. Its webhook queue may be holding the data you need.
- Is the scenario on? If it’s off, open its history and find the run that errored. That error is the cause.
- What starts it? A scenario with an instant trigger is switched off after its first error. For the others, you set how many errors in a row Make allows.
- Is anything in the webhook queue? Check the webhook’s queue in Make. Those are the records that arrived while the scenario was off.
- Are incomplete executions stored? With “Store incomplete executions” on, a failed run is paused in the incomplete executions folder so it can be resolved. With it off, the run stops and rolls back.
- Does a connection say “reauthorize”? An expired Google, Outlook or CRM connection stops every scenario that uses it. See connections that keep expiring.
- Did several scenarios stop at once? Then the cause is shared: one connection, one app, or a Make outage.
// DEACTIVATED
Why Make deactivates a scenario
Make stops a scenario that keeps failing. You choose how many errors in a row a scenario gets. One that starts from an instant trigger ignores that setting and stops on the first error. A scheduled scenario that starts from a webhook stops after 3 errors.
Owners on the Make Community describe waking up to all their lead scenarios switched off at once, after the same error hit every one, with leads still coming in from their ads and going nowhere.
// THE QUEUE
What happens to data while it’s off
Each Make webhook keeps its own queue, and requests are kept there while the scenario is off. When you turn the scenario back on, Make asks whether to process the queued data or delete it. Process it.
The limits that matter:
- Queue size: 667 items for every 10,000 credits licensed a month, up to 10,000. Over the limit, Make rejects the rest with “Queue is full”.
- Unattached webhooks: a webhook not connected to any scenario for more than 5 days is deactivated, so deleting a scenario can take its hook with it.
- A webhook that is itself off stores nothing. Data sent to it is gone.
// HOW WE STOP IT
Prevention, detection, a register and a replay
An error notice only comes when something runs and fails. If the webhook stops arriving, nothing runs.
Prevention: our own account in your system
Connections run through a dedicated Web Blend user: Web Blend business name, an @webblend.au email, only the rights the automation needs. A staff password change or a deleted user can’t break it. You know it’s there and leave it alone.
Detection: an alert when a flow goes quiet
Error alerts need a run that fails. A trigger that stopped produces no run at all. So an n8n automation watches each flow for silence, for example no form leads in 3 days or no review requests sent, and alerts us.
Fail-safe: a register
Every action is logged to a Google Sheet, such as who was asked for a review. When something fails, the sheet shows exactly who missed out.
Recovery: a replay
A catch-up automation replays each missed action once, or backdates the data, such as conversions to Google Ads, so it catches up.
// PRICING
Automation Rescue + Watch
$490 + GST to fix what’s broken and set up monitoring, then $49/month + GST.
For any business running Make scenarios, including ones we didn’t build. We watch n8n too, including self-hosted n8n. See every symptom we fix on automation monitoring for small business.
-
We find why the scenario stopped and fix it - We clear the queue and replay what was missed, once each
- We move connections onto a dedicated Web Blend account
- We add the silence alert and the register
- You get a plain-English note of what broke and what changed
// FIT
When you don’t need us
-
You read Make’s error emails the day they land and know your way around the scenario history. - The scenario is a nice-to-have and nobody outside the business relies on it.
Need a new build, not a fix? Start at business automation. Running Zapier as well? See Zapier stopped working.
// QUESTIONS
Questions owners ask
Not sure why your scenario stopped? Tell us which one and roughly when.
Ask usWhy did Make deactivate my scenario?
It errored. A scenario that starts from an instant trigger is switched off after its first error. Others stop after the number of consecutive errors set in the scenario settings. Open the scenario history and find the failed run.
Will I lose the data that arrived while it was off?
Not if it reached the webhook queue and the queue wasn’t full. When you turn the scenario back on, Make asks whether to process the queued data or delete it: choose process. If the webhook itself was off, the data was never stored.
My scenario is on but nothing comes in. Why?
The source stopped sending. A lead form webhook that failed to register, an expired connection or a changed form can all leave a scenario on and idle, with no error anywhere.
Should I rebuild the scenario from scratch?
Not first. A rebuild can come with a new webhook address and leave the old queue behind, and Make deactivates a webhook that isn’t connected to a scenario for more than 5 days. Fix the cause, clear the queue, then decide.
Can you watch scenarios you didn’t build?
Yes. Watch covers Make and n8n automations whoever built them, including self-hosted n8n. It starts with the $490 + GST fix, which moves the connections onto our account and sets up the alert and the register.
How much does it cost to fix a Make scenario?
Automation Rescue + Watch is $490 + GST to fix what’s broken and set up monitoring, then $49/month + GST.
// GET HELP
Get it running, and hear about the next stop first
Tell us which scenario stopped and roughly when. We’ll tell you what probably broke and give you a fixed price to fix it and watch it.
// AUTOMATION RESCUE + WATCH
Tell us what stopped
Say what went quiet and roughly when. A person at Web Blend replies within one business day with what probably broke and a fixed price to fix it and watch it.
Documentation used
- Make: scenario settings (errors before deactivation, incomplete executions)
- Make: webhooks (queue limits, 5-day deactivation)
- Make Academy: scenarios and webhook queues