A Next Gen Zap stops running when it is turned off, or when Zapier cannot set up or keep its trigger. Its runs can also be held or fail. Learn how to find the cause and get your workflow running again.
Available on plans:
Free
Professional
Team
Enterprise
Next Gen Zaps is in early access by request. Sign up at https://zapier.com/workflow/early-access. If you’re on a Team plan, the request must come from an account owner or admin. If you’re on an Enterprise plan, contact Support for access. This feature has limited availability and is in active development.
To find the cause, open your workflow. In the Zapier left sidebar, click Automations, select Next Gen Zaps in the second sidebar, then click the workflow. It opens in the Workflow Manager. Then find the problem below that matches your workflow.
Your Next Gen Zap is turned off
Symptom
In the Workflow Manager, the toggle switch next to the workflow name is off. New events in your trigger app do not start the workflow, and no new runs appear on the Runs tab.
Causes
- The workflow is not published. A draft does not run, and you can only turn on a workflow after you publish it.
- Your AI tool published the workflow without turning it on. When an MCP client publishes a draft, the workflow keeps its current on or off state. A new workflow is turned off when it is created.
- Someone turned the workflow off.
- Zapier turned the workflow off because of its trigger. Learn more in Zapier turned off your Next Gen Zap because of its trigger.
How to fix it
- Open the workflow in the Workflow Manager.
- If the workflow is not published, publish the draft. On the right of the bar above the canvas, click Publish, then click Publish in the dialog box. Publishing from the Workflow Manager turns the workflow on.
- If the workflow is published, click the toggle switch next to the workflow name to turn it on. You can also ask your AI tool to turn the workflow on.
If a message says that you do not have permission, ask the workflow's owner, a super admin, or the account owner to turn it on.
While a Next Gen Zap is off, its trigger does not receive events. Zapier does not run those events after you turn the workflow back on.
Zapier turned off your Next Gen Zap because of its trigger
Symptom
Your Next Gen Zap is turned off, but nobody turned it off. Right after you publish, one of these messages can appear in the Workflow Manager:
- Your Zap couldn't turn on
- Your Zap didn't turn on
A workflow that ran before can also stop running and turn off.
Causes
When you publish a workflow that has a trigger, Zapier sets up the trigger. If Zapier cannot set up the trigger, the workflow does not turn on.
After Zapier sets up the trigger, Zapier turns the workflow off if the trigger stops working. This can happen for these reasons:
- The app connection that the trigger uses needs reconnecting, or its access was revoked.
- The trigger app or Zapier ended the trigger, for example after an error.
- The app connection, the user, or the account that the trigger uses was deleted.
- The trigger did not fire for a long time, so Zapier removed it.
A problem with the trigger's app connection turns off the whole workflow. A problem with the app connection of a later step holds the run instead. Learn more in Runs are held.
How to fix it
- Open the workflow in the Workflow Manager.
- If Your Zap couldn't turn on appears, click Review trigger.
- Fix the trigger or its app connection. For example, reconnect the app account that the trigger uses. You can describe the change to Zapier in the Chat panel, or ask your AI tool to make it.
- Publish the workflow again. Zapier sets up the trigger again, and Turning on your Zap appears while it works. This can take a few minutes.
- Wait until a message confirms that your Zap is on.
Learn more about how to confirm that Zapier set up the trigger.
Your Next Gen Zap has no trigger
Symptom
Your workflow is published and turned on, but it never starts by itself. Runs appear on the Runs tab only when you or your AI tool run the workflow.
Causes
A Next Gen Zap with no trigger runs only on demand.
How to fix it
- To run the workflow now, make sure it is published and turned on. Then open it in the Workflow Manager and click Run. You can also ask your AI tool to run it.
- To start the workflow automatically, add a trigger, such as a schedule, a webhook, or an app event. Learn how to choose how a Next Gen Zap starts.
Runs are held
Symptom
On the Runs tab, one or more runs have the Held status, and they do not continue.
Causes
Zapier holds a run when the run cannot continue until something is fixed. A held run stays held until you release it or cancel it. The status in the list of runs tells you why Zapier held the run:
| Status in the list | Why Zapier held the run | What to do |
|---|---|---|
| Held · Reconnect needed | A connection that the run uses expired or is no longer valid. | Click Reconnect in the Held run section, and reconnect the app. Then release the run. |
| Held · Task limit reached | Your account reached its task limit. | Click Upgrade to change your plan. Then release the run. |
| Held · Processing limit reached | Your account reached its daily processing limit. | Wait until the limit resets. The Held run section shows when. Then release the run. |
| Held | Another issue stopped the run. | Check the step details, and fix the issue. Then release the run. |
How to fix it
- Open the workflow in the Workflow Manager.
- In the center of the menu bar above the canvas, click the Runs tab.
- Select the held run. The Held run section explains why Zapier held it.
- Fix the issue that the Held run section names.
- In the Held run section, click Release.
The run continues from the step where Zapier held it. If Zapier held the run before it started, the run starts from the beginning. You can release one run at a time.
When a connection caused the hold, the Release button is unavailable until you reconnect the app. Only the workflow's owner or a super admin can release a run.
Runs fail
Symptom
On the Runs tab, one or more runs have the Failed status. Zapier emails the workflow's owner each time a published run fails, unless agentic management sends its own email about that failure.
Causes
- A step failed on every retry. By default, Zapier tries each step up to five times. If the step still fails, the run fails, and the step has the Exhausted status.
- The run took too long. A run fails if its steps run for more than 30 minutes in total. Time spent in a delay or waiting for a callback does not count.
- The workflow has a Code by Zapier step. From November 17, 2026, a Next Gen Zap that still has a Code by Zapier step stops with an error at that step. This can happen in a workflow that you imported from a Classic Zap.
Learn about other Next Gen Zap limitations that can cause a run to fail.
How to fix it
- Open the workflow in the Workflow Manager.
- In the center of the menu bar above the canvas, click the Runs tab.
- Select the failed run.
- In the Error section, click Explain error. Zapier explains in the chat why the run failed and how to fix it.
- Ask Zapier in the Chat panel to fix the workflow, or ask your AI tool. The change goes into a draft.
- Test the draft, then publish it.
- To run the failed run again with the same input, select the run and click Re-run. The new run uses the version that is live now.
If the workflow has a Code by Zapier step, ask Zapier to rebuild the step in code. You can also turn off the Next Gen Zap and turn your original Classic Zap back on.
If agentic management is on, an agent reviews each failed run and works out a fix. You choose whether the agent applies fixes on its own or asks you first. Even when it applies fixes on its own, it asks for your approval when a fix is higher risk or relies on a guess.
Only the workflow's owner or a super admin can re-run a run. Only the workflow's owner, a super admin, or the account owner can edit a workflow.
Still need help?
If this article did not fix the issue:
- Ask in the Zapier Community. Get advice from experienced Zapier users.
- Learn more about getting help and support with Zapier.