Zapier · Zap run status

On hold (held Zap run)

Short answer

An On hold Zap run is waiting for an issue to be fixed before it can continue. Fix the cause, such as a disconnected app, a reached task limit or a payment issue, then replay the held run.

VerifiedLast verified

01Error text

Zapier error
On hold

02Likely causes

  • Flood protection held the runs because 100 or more steps were triggered.
  • An app account is disconnected, or access to a connection was revoked.
  • The task limit was reached, or the Zap uses a premium app that is not in the plan.
  • Payment information expired, the trial ended or the plan changed.
  • An app access policy on an Enterprise account restricts the app.
  • The Zap has more than 100 steps.

03How to fix it

  1. For too much data, use a delay after queue action.
  2. For a disconnected app, reconnect the app account. For revoked access, ask the connection owner to share the connection again.
  3. For a task limit, upgrade the plan. For a payment issue, update the payment method.
  4. For an app access policy, ask the owner or admin to allow the app.
  5. For the step limit, split the workflow into two or more Zaps.
  6. Replay the held run.

iNotes

While a run is held, Zapier keeps the trigger data, so no data is lost once the cause is fixed.

04Official documentation

Test every fix in a non-production environment before you apply it to production. See how entries are verified.

More for Zapier work:Open Zapier jobsZapier rates and salaries

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.