Zapier · error message

Zapier: Task was stopped because its Zap was turned off

ConfigurationZap and run status

Last verified

The exact message
Task was stopped because its Zap was turned off

What it means

This message appears in the run details in Zap history. It means a run was already in progress when the Zap was switched off, so Zapier stopped the remaining steps. Older versions of the message add "during its execution".

Zapier's help center lists three causes: you (or a teammate) turned the Zap off while it was running; the Zap errored too many times and Zapier turned it off mid-run; or there was an issue or outage with an app or with Zapier. The second is the one that surprises people, because the visible message is about the Zap being off, while the real problem is the errors that came before it.

What is not wrong: the step that shows this message usually did nothing wrong itself. Look earlier in Zap history for the runs that errored.

What it looks like

Zap history > Run details
Status: Errored
Task was stopped because its Zap was turned off

Why it happens

  • Someone turned the Zap off, or edited and republished it, while runs were in progress.
  • The Zap hit the automatic turn-off threshold for errors and was switched off mid-run.
  • An outage at Zapier or at one of the connected apps.
  • A plan change removed access to a feature the Zap uses, turning it off.

How to fix it

  1. Open Zap history, filter to Errored runs and read the earliest errors before the stop.
  2. Fix the underlying errors (reconnect accounts, correct field mappings).
  3. Turn the Zap back on; if it will not turn on, follow the "Zap could not be turned on" guidance.
  4. Check status.zapier.com and the connected app's status page for outages at that time.
  5. Replay the stopped runs from Zap history once the Zap is working.

How to stop it recurring

Turn on error notifications so you hear about failures before the Zap is switched off, use error handlers or Paths for expected failure cases, and avoid editing live Zaps during busy periods. See why Zapier turns Zaps off automatically.

Official documentation: help.zapier.com/hc/en-us/articles/16815648307853-Error-Task-was-stopped-because-its-Zap-was-turned-off. See all Zapier error messages or the Zapier limits and quotas.

Related errors

Definitions

Quick answers

What does "Task was stopped because its Zap was turned off" mean in Zapier?

This message appears in the run details in Zap history. It means a run was already in progress when the Zap was switched off, so Zapier stopped the remaining steps. Older versions of the message add "during its execution".

How do I fix "Task was stopped because its Zap was turned off"?

1. Open Zap history, filter to Errored runs and read the earliest errors before the stop. 2. Fix the underlying errors (reconnect accounts, correct field mappings). 3. Turn the Zap back on; if it will not turn on, follow the "Zap could not be turned on" guidance. 4. Check status.zapier.com and the connected app's status page for outages at that time. 5. Replay the stopped runs from Zap history once the Zap is working.

Error handling you can see in the workflow

Autonoly workflows have per-node retries, timeouts, continue-on-fail and error-handler branches, so a failing step can be retried or routed instead of stopping the whole run. Saved workflows have no loop node; lists are worked through by the AI agent or one run per trigger item.

Also see Visual workflow builder.