When a large number of triggers or actions occur within a short time span, they are throttled (limited) to reduce their frequency. This is known as rate limiting and may be applied by Zapier or by your connected third-party app.
Rate limits and throttling in ZapierLast updated:
If you’re on the Free plan or on a trial, your Zap can error saying it has been throttled if too many actions go through in a short time span. The limit is approximately 200 actions every 10 minutes per Zap. This limit does not apply to paid accounts.
There is a limit of 105,000 records to check for new data. If your trigger contains more than this number, the Zap trigger may error.
Many third-party apps and services have their own API limits and throttling mechanisms. To distinguish between third-party errors and Zapier throttling errors, look for "Zapier" in the error message.
If you have a large number of items (100+) that trigger a Zap at once, Zapier holds them for you and sends you an email requesting your confirmation. This helps to prevent a large number of actions from running by mistake and protects your task limit.
Once you confirm these should be played, you can use the Replay feature to let them continue. These replayed Zap runs are processed at a rate of 1 per second. For example, 1,000 Zap runs will take a little over 15 minutes to complete.
If you don't want these Zap runs to go through, you can delete them.
Instant triggers are not subject to flood protection, as each item is sent to the trigger individually. Some exceptions include Google Sheets and Google Calendar "New Event" and "Updated Event" instant triggers, which use both webhook and polling techniques.
- Each user’s webhooks are subject to a 429 status code rate limit after 10,000 requests in a 5-minute window. This includes subscription webhooks and REST Hooks.
- Each individual webhook will return a 429 status code after 30 requests per second, to encourage a smooth delivery of hooks instead of massive bursts. This includes subscription webhooks and REST Hooks.
- Legacy webhook routes without the user ID in the URL will return a 429 status code after 1,000 requests received in a 5-minute window (per webhook route). This includes subscription webhooks and REST Hooks.
- During heavy periods of sustained webhook activity, Zapier may return a 200 status but still delay the processing of your webhooks by several minutes.
- If you want to ensure delivery of webhooks, retry delivery on anything besides a 200 status code from Zapier and use an industry-standard exponential backoff interval for retries.
- Code Steps are limited to 75 runs every 10 seconds.
- The Free plan can run scripts of up to 1 second and 128 MB of RAM. Paid plans can run scripts of up to 10 seconds and 256 MB of RAM. Your Zap will error if it exceeds these limits.
When using a private app, you may encounter an error like
Unpromoted apps can only do 100 calls every 60 seconds. This is due to a built-in limit for preventing spam for private apps. Once the app has gone public, this limit on script executions is lifted.
Need more help?