How to troubleshoot held Zap or step runs

If your Zap or step run is held, it can be due to several causes. This article explains how to troubleshoot held runs.

Causes

Held statuses can be caused by:

  • Too much data: when Zapier checked for new data, too many steps (100+) were triggered. This is called “flood protection" and prevents your Zap from accidentally using a large number of tasks.
  • Disconnected app: one of the app accounts used in the Zap is disconnected.
  • Connection access revoked: on Team or Enterprise accounts, the Zap owner lost access to an app connection used in the Zap. This can happen when a connection owner stops sharing the connection, when a member is removed from the account, when an admin changes connection sharing settings, when the Zap owner's role is downgraded from Admin or higher to Member (including role changes from account ownership transfers), or when a connection's ownership changes (for example, promoting a personal connection to a managed connection).
  • Task limit reached: the account reached the task limit for its plan or used a premium appthat is not available in your Zapier plan.
  • Payment issue: the payment information on the account expired and must be updated.
  • Team plan downgrade: the account moved from a Team or Company plan to a plan without team features.
  • Trial ended or plan changed: a free trial ended, or the account switched to a different plan. The new plan does not include features the Zap uses.
  • App access policy: on Enterprise accounts, the Zapier account owner or admin has limited the use of the app, and you do not have permission to use it. This can happen when:
    • The app is on the account's restricted apps list.
    • The app is not on the allowed apps list.
    • An admin changed the account's app access setting, and the app was not added to the new list.
  • Step limit reached: the Zap has more than 100 steps.

While a run is held, Zapier continues to store trigger data. Once you fix the cause, you can replay the held runs, and no data is lost.

How to fix it

Too much data

Use a delay after queue action to run tasks at a slower pace. After your Zap triggers, it will add actions to the queue, which are then processed one by one in the order they were added.

Disconnected app

Reconnect the app account, then replay your held Zap run.

Connection access revoked

The Zap owner must have access to every app connection used in the Zap. If the owner lost access to a connection, they can:

  • Ask the connection owner to share the app connection again.
  • Update the affected step to use a connection they already have access to.
  • If the Zap owner's role was downgraded (for example, from Admin to Member, or after an account ownership change), ask an account admin to restore the role or re-share the affected connections.
  • If a connection's ownership changed (for example, a personal connection was promoted to a managed connection), ask the new connection owner or an admin to share the connection with the Zap owner.

Once the Zap owner has access to every connection in the Zap, turn the Zap back on and replay any held runs.

Task limit reached

Upgrade your Zapier plan, then replay your held Zap run.

Payment issue

Update your payment method, then replay your held Zap run.

Team plan downgrade

Check your current plan on your billing page, then do one of the following:

Trial ended or plan changed

Check your current plan on your billing page, then do one of the following:

App access policy

The solution depends on your account's app access policy:

  • If your account uses restricted apps: Ask your account owner or admin to remove the app from the restricted list, or add an exception for your member account or team.
  • If your account uses allowed apps: Ask your account owner or admin to add the app to the allowed list.
  • If your admin recently changed your account's app access setting: The app may not yet be on the new list. Ask your admin to add it.

Once the app is permitted, replay your held Zap run.

Note

App access policies affect both Zap workflows and Agents. If an Agent uses an app that is restricted, or not on the allowed list, it may not run as expected.

Step limit reached

Split your workflow into 2 or more Zap workflows.

Was this article helpful?
227 out of 234 found this helpful