Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Zapier turned my Zap off by itself after errors

Short answer

Zapier turns off a Zap that errors 95 percent of the time it runs, if it has run more than 20 times in the past 7 days. Find the failing step first, replay what failed, and only then switch it back on, otherwise it fails again.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • My Zap was on yesterday and is off today and I did not touch it.
  • Zapier sent an email about errors.
  • Orders or leads stopped arriving in the next app.
  • Zap history shows a long run of red errors.
  • I switched it on again and it stopped again.

Why does this happen?

  1. The error ratio rule

    Zapier turns off a Zap that errors 95 percent of the time it runs and has run more than 20 times in the past 7 days. On Team and Enterprise accounts an email and a grace period come first, and on Professional, Team and Enterprise plans an Error ratio override can keep a Zap running despite errors.

  2. Something changed in a connected app

    A password reset, a removed user, a renamed field or an expired connection makes every run fail in the same step. The rule then fires because the failures are constant.

  3. The Zap lost access to a connection

    Zapier says a Zap pauses if its owner loses access to an app connection used in it, such as when a connection stops being shared or the owner's role changes.

  4. Autoreplay can hide the problem for a while

    With autoreplay on, Zapier replays runs with an errored status, but it is not available on the Free plan and a Zap that is off is not replayed. Errors can pile up unnoticed until the Zap is shut off.

What can I do about it today?

  1. Open Zap history and read the first errorThe first failed run, not the latest, usually says what changed. Copy the message and the date.
  2. Check the app connectionsReconnect any connection marked as expired and note who owns it.
  3. Do not just switch it back onTurning it on with the cause unfixed fills history with more errors and can repeat actions that half-succeeded.
  4. Look at what was missedCompare the failed runs with the records in the destination app so nothing is lost silently.
  5. Think before using the overrideKeeping a failing Zap running hides a real fault. Use it only if you know why errors are expected.

When should I bring someone in?

  • Failed runs involve payments, invoices or customer messages.
  • The Zap fails again right after you reconnect.
  • Nobody knows who owns the connection or the Zap.

How do I handle it?

  1. Read the failure historyI find the first error, the step it happened in, and what changed in that app on that date.
  2. Fix the cause, not the symptomCredentials, field changes or access are corrected at the source.
  3. Recover missed workI compare failed runs with the destination and replay only what is missing, checking for duplicates first.
  4. Add a signalAn alert goes to a named person on the first failure, so the 95 percent rule is never how you find out.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is the data from the failed runs lost?

Failed runs stay in Zap history and can be replayed manually. Replay is not available for every status on the Free plan.

Can I stop Zapier doing this?

On Professional, Team and Enterprise, an error ratio override keeps a Zap on. It does not fix the errors.

Will a replay count as tasks?

Replaying an entire run counts successful steps towards task usage again, Zapier states.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.