Zapier: Your Zap could not be turned on
Last verified
Your Zap could not be turned onWhat it means
Zapier shows this when you try to publish or turn on a Zap and one of its checks fails. For instant triggers, turning a Zap on usually registers a webhook subscription with the trigger app, so the message often reflects that app refusing or failing the subscription request. Zapier typically appends a reason after the main message.
Common reasons are incomplete steps, a disconnected or expired account, missing permissions in the trigger app, or a feature that your plan does not include. Community reports show it with app-specific details such as missing authentication and with no extra detail at all.
What is not wrong: the Zap's logic may be fine. The failure is in setting it up to run, not in a run.
What it looks like
Your Zap could not be turned on
<reason from Zapier or the trigger app>Why it happens
- A step is incomplete or has an unresolved error in the editor.
- The trigger app account is disconnected, expired or lacks the permission needed to create a webhook.
- The Zap uses a premium app or multi-step feature not available on the current plan.
- The trigger app's API rejected or timed out on the subscription request.
How to fix it
- Read any text after the main message; it usually names the step or reason.
- Open each step and complete any fields marked as required; retest the trigger.
- Reconnect the trigger app account under Apps and confirm it has admin or webhook permissions.
- Confirm your plan includes every app and feature the Zap uses.
- Try again after a few minutes in case the app was temporarily unavailable; contact Zapier Support with the Zap ID if it persists.
How to stop it recurring
Test every step before publishing, use service accounts with stable permissions for trigger apps, and review plan limits before building multi-step or premium Zaps.
Official documentation: help.zapier.com/hc/en-us/articles/8496216132621-Zap-is-not-running. See all Zapier error messages or the Zapier limits and quotas.
Related errors
Definitions
Quick answers
What does "Your Zap could not be turned on" mean in Zapier?
Zapier shows this when you try to publish or turn on a Zap and one of its checks fails. For instant triggers, turning a Zap on usually registers a webhook subscription with the trigger app, so the message often reflects that app refusing or failing the subscription request. Zapier typically appends a reason after the main message.
How do I fix "Your Zap could not be turned on"?
1. Read any text after the main message; it usually names the step or reason. 2. Open each step and complete any fields marked as required; retest the trigger. 3. Reconnect the trigger app account under Apps and confirm it has admin or webhook permissions. 4. Confirm your plan includes every app and feature the Zap uses. 5. Try again after a few minutes in case the app was temporarily unavailable; contact Zapier Support with the Zap ID if it persists.
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.