// AUTOMATION FIXES

Zapier stopped working? Find what went quiet, then stop it happening again

Zapier stopped working usually means a Zap that ran for months has gone quiet: no new runs, no error email, and a test that still passes. The trigger stopped sending, a connection expired, or Zapier turned the Zap off. Web Blend builds and runs Zapier, Make.com and n8n automations for trade and service businesses, and is a ServiceM8 Bronze Partner. We fix the Zap, then watch for silence so the next one is caught before a customer complains.

Updated October 2026. Zapier behaviour checked against Zapier’s help centre on 30 October 2026.

5.0 from 16 Google reviews
Example alert that a quote form Zap went quiet: no runs in 3 days and no error email, above a status card showing the Zap is on, its test passes, its last run was 3 days ago and no errors since Example
Example: a Zap that is on and passes its test but has not run for 3 days, with no error email. Mock-up with fictional data.

// CHECK IT NOW

Six checks before you rebuild the Zap

It’s a common one. The Zapier Community has thread after thread of Zaps that ran for months, still pass the test, and no longer trigger.

  1. Is the Zap still on? Open the Zap. If it’s off, look at its change history for why.
  2. When did it last run? Open Zap history and filter to this Zap. A last run days ago with no errors after it means the trigger stopped sending, not that a step failed.
  3. Are runs held? When an account hits its task limit, Zapier holds every action in every Zap until the limit resets or the plan is upgraded.
  4. Is the connection still live? Open your app connections. Anything asking to reconnect has stopped the Zaps that use it. See Zapier connection expired.
  5. Are error emails on? In notification settings, “Never” means you won’t hear about failures. Zapier also sends no error email when an error handler runs.
  6. Did the source app change? A renamed field, a new form or a retired integration can stop a trigger with nothing in Zapier to show for it.

// TEST VS LIVE

Why the test passes and live runs never arrive

A test pulls a sample the trigger app already holds. A live run needs each new record to reach Zapier as it happens. When that breaks, the test still passes and nothing else happens. Owners report it with Messenger, booking and CRM triggers alike.

Compare what failed with what worked: the same form, the same page, the same kind of record? If only some records go missing, the problem sits upstream of Zapier.

// TURNED OFF

When Zapier turns a Zap off for you

Zapier turns a Zap off when it errors 95% of the time it runs and has run more than 20 times in the past 7 days. On Team plans the account owner gets an email and 24 hours’ grace first; on Enterprise, 72 hours. Fix the errors in Zap history, then turn the Zap back on.

// HOW WE STOP IT

Prevention, detection, a register and a replay

Example silence check for a new lead flow: 4 and 5 runs on Monday and Tuesday, then no runs Wednesday to Friday, an alert after 3 quiet days, and 9 missed leads replayed once each after the fix Example
Example: the silence check on one Zap. Three days with no runs sends the alert, then each missed lead is replayed once. Mock-up with fictional data.

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, plus the Zapier add-on, $29/month + GST per Zapier account, to watch your Zaps. Each Zap gets a heartbeat step and its own check.

Rather have it all in one place? We can move your Zaps to Make or n8n instead, quoted from $490 + GST, and the standard $49/month + GST then covers them. Running more than Zapier? See automation monitoring for small business.

What you get
  • We find why the Zap stopped and fix it
  • We move the connection onto a dedicated Web Blend account
  • We replay what was missed, once each
  • 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

  • One Zap, low stakes, and you check Zap history weekly: turn error emails on and keep checking.
  • You want an alert only and will fix things yourself: a self-serve monitoring tool will do.

Want a brand new automation, not a fix? Start at business automation. Running Make instead? See Make scenario stopped running.

// QUESTIONS

Questions owners ask

Not sure why your Zap went quiet? Tell us which one and roughly when.

Ask us
Why did my Zapier Zap stop working with no error?

Because nothing ran. An error needs a run that fails. If the trigger app stopped sending, the connection expired or runs are held at your task limit, there is no failed run to report.

Why does my Zap test work but not run on real leads?

The test uses a sample the app already holds. Live runs need each new record to reach Zapier as it happens. If that breaks, tests keep passing. Check whether some records arrive and others don’t, and how the missing ones were created.

Does Zapier turn Zaps off automatically?

Yes. Zapier’s help centre says a Zap is turned off when it errors 95% of the time it runs and has run more than 20 times in the past 7 days. Team and Enterprise accounts get an email and a grace period first.

Can you get back the leads my Zap missed?

Often, if the source app still holds the records: our catch-up automation replays each one once. For Google Ads, Google keeps the click ID for 90 days, so click conversions older than that can’t be uploaded. Sooner is better.

Do you fix a Zap someone else built, or rebuild it?

We fix it in place, on a connection your staff can’t break, and watch it with the Zapier add-on. If you’d rather move off Zapier, we rebuild the Zaps in Make or n8n instead, quoted from $490 + GST.

How much does it cost to fix a Zap that stopped?

Automation Rescue + Watch is $490 + GST to fix what’s broken and set up monitoring, then $49/month + GST, plus the Zapier add-on, $29/month + GST per Zapier account.

// GET HELP

Find out what stopped before a customer does

Tell us which Zap went quiet and roughly when. We’ll come back with what probably broke and a fixed price: $490 + GST, then $49/month + GST plus the $29/month + GST Zapier add-on.

// 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.

We use these details to look into what stopped and reply. No spam. See our privacy policy.

Documentation used

// BEFORE YOU GO

Get the automation health checklist

The checks we run to find automations that can stop without telling anyone, sent by a person at Web Blend with a note on where to start. Work through it in an afternoon.

  • When each Zap, scenario or workflow last ran
  • Which connections hang off one staff login
  • A silence alert, a register and a replay plan for each flow

A person at Web Blend sends this, usually within one business day. No list, no spam. See our privacy policy.