How to troubleshoot held Zap or step runs

Written by Owner

Updated at August 20th, 2025

+ More

Table of Contents

Causes How to fix it Too much data Disconnected app Task limit reached Payment issue Restricted app Step limit reached

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.
Task limit reached: the account reached the task limit for its plan or used a premium app that is not available in your Zapier plan.
Payment issue: the payment information on the account expired and must be updated.
Restricted app: in Team or Enterprise accounts, the Zapier account owner or admin has limited the use of the app, and you do not have permission to use it.
Step limit reached: the Zap has more than 100 steps.

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.

Restricted app

Ask your account owner or admin to remove any restrictions on using the app, or use another app. Explore all apps available on Zapier.

Step limit reached

Split your workflow into 2 or more Zaps.

How to troubleshoot held Zap or step runs

Contact Us

Causes

How to fix it

Too much data

Disconnected app

Task limit reached

Payment issue

Restricted app

Step limit reached

Related Articles