Tier | Notifications |
---|---|
Free tiers | You’ll receive an email when you reach 100% of your daily usage. |
Paid tiers | You’ll receive an email at 80% and 100% of your included credits for your billing period. |
413 Payload Too Large
status code when the body of your request exceeds .
Pipedream supports two different ways to bypass this limit. Both of these interfaces support uploading data up to 5TB
, though you may encounter other platform limits.
pipedream_upload_body=1
query string or an x-pd-upload-body: 1
HTTP header in your HTTP request. Read more here.429 Too Many Requests
response. If you control the application sending requests, you should retry the request with exponential backoff or a similar technique.
We’ll also accept short bursts of traffic, as long as you remain close to an average of 10 QPS (e.g. sending a batch of 50 requests every 30 seconds should not trigger rate limiting).
This limit can be raised for paying customers. To request an increase, reach out to our Support team with the HTTP endpoint whose QPS you’d like to increase, with the new, desired limit.
/tmp
directory.
This limit cannot be raised.
Tier | Maximum time per execution |
---|---|
Free tiers | 300 seconds (5 min) |
Paid tiers | 750 seconds (12.5 min) |
Tier | Events retained per workflow |
---|---|
Free tiers | |
Paid tiers | View breakdown of events history per paid plan |
console.log()
statements, step exports, and the original event data sent to the workflow cannot exceed a combined size of . If you produce logs or step exports larger than this - for example, passing around large API responses, CSVs, or other data - you may encounter a Function Payload Limit Exceeded in your workflow.
This limit cannot be raised.