Troubleshooting
Zapier operating constraints
Zapier offers a relatively unique run-time environment for your integration and its requests to your API. The environment is stateless and restricts both execution time and payload size to offer normalized reliability and running time. There are three distinct contexts of this run-time that your integration will need to consider.
- Zap step setup and testing using the Zap editor
- Zap startup - turning a Zap on
- Zap step execution when a Zap runs
zapier logs command.
Important Zapier constraints summary
| Time Limits | |
|---|---|
| Zap Editor test step: request(s) + scripting | 30 seconds |
| Polling trigger: request(s) + scripting | 30 seconds |
| REST Hook trigger: ingest and payload processing scripting | 30 seconds |
| Create/search action: requests(s) + scripting | 30 seconds |
| Size limits | |
|---|---|
| Deduplication table | 105,000 rows per Zap |
| Custom fields | 1000 |
| Webhook payload | 10 MB |
| Trigger/Action input payload | 6 MB |
| HTTP response payload | 20 MB |
| Downloaded files | ~120 MB |
| Throttles | |
|---|---|
| Polling trigger | Default: 100 new items/poll |
| REST Hook trigger | 10000 webhooks/5 minutes |
| 30 webhooks/second | |
| More on throttles here. |
| TCP/IP | |
|---|---|
| Integration assigned IP | AWS-East |
Need help? Tell us about your problem and we’ll connect you with the right resource or contact support.