Workflow System Limits
There are various limits enforced by PagerDuty Workflow Automation, but we believe your work shouldn’t stop because of these limits. The most you’ll likely notice is the occasional task or instance that takes a bit longer to complete because the scale of the automation.
When you reach a limit, our system manages the issue on its own or provides immediate feedback. For example, if an uploaded file is too large we provide immediate feedback. If too many tasks start at once, the work will be smartly queued and completed as soon as possible without interrupting your work.
Limits ensure a high-quality experience for you and your team and help limit interruptions to processes and actions.
What are the current system limits?
Actions
| Feature | Current Limit |
|---|---|
| Max actions started | 10/second/team |
| Max actions executing concurrently* | 8/team |
*If exceeded, actions are queued and executed as soon as possible.
Instances
| Feature | Current Limit |
|---|---|
| Total number of fields per instance | 1,000 |
| Total number of tasks per instance | 1,000 |
| Field size (non-file)** | 128kB |
| Total field size per instance | 10MB |
| Instance starts per team*** | 10/second/team |
| Instance starts per process*** | 1/second/team |
**The field size is the maximum data available per field, but not the maximum file size. For example, 128kB is around 122,000 characters, or 20,500 words, or 82 solid pages of text. A fix task is created if a Workflow tries to save more than 128kB to a field.
***If exceeded, instances are queued and executed as soon as possible.
Data Table
Master and Application Data tables
| Feature | Current Limit |
|---|---|
| Columns | 100**** |
| Rows | 100,000**** |
| Cells | 5,000,000**** |
| Cell Size | 64kB of data |
If a master or application data table exceeds 100,000 rows, the oldest instances over 100,000 will not be visible. If you export the table, only the last 100,000 rows are exported.
Imported Data Tables
| Feature | Current Limit |
|---|---|
| Columns | 100**** |
| Rows | 100,000**** |
| Cells | 5,000,000**** |
| Cell Size | 128kB of data |
| Total cell size within a table | 1GB total cell size |
****Column, row, and cell limits
PagerDuty Workflow Automation employs soft and hard limits to ensure a high-quality experience for you and your team and help limit interruptions to processes and actions.
Performance can degrade significantly after the soft limit. If the hard limit is reached, a fix task is created.
| Soft limit | Hard limit | |
|---|---|---|
| Columns | 100 | 500 |
| Rows | 100,000 | 150,000 |
| Cells | 5,000,000 | 15,000,000 |
General
| Feature | Current Limit |
|---|---|
| Batch Size | 10,000 |
| Insert Data Table into Excel Template | 10,000 rows and 50 columns |
| Data Table to Markdown | 1,000 rows and 50 columns |
| Data Table to Text | 1,000 rows |
| Data Table in a web form | 2,000 rows |
A data table shown in a web form loads its rows when the form opens. If the table has more than 2,000 rows, the form loads the first 2,000 and tells you above the table that there are more. The table itself still holds every row, and the rest are available everywhere else the table is used.
Excel
| Feature | Current Limit |
|---|---|
| File Size | 100MB |
CSV
| Feature | Current Limit |
|---|---|
| File Size | 1GB |
File
| Feature | Current Limit |
|---|---|
| Import/Export | 100MB |
Email
| Feature | Current Limit |
|---|---|
| Outbound Email (including attachments) | 7.5MB |
| Inbound Email (including attachments) | 30MB |
| Maximum number of recipients per email action | 50 recipients |
PPTX
| Feature | Current Limit |
|---|---|
| File Size | 100MB |
Optical Character Recognition (OCR)
| Feature | Current Limit |
|---|---|
| Scanned Image Size | 7.5MB |
| PDF page limit | 2000 pages |
API
| Feature | Current Limit |
|---|---|
| General API calls | 100/second/user |
| Incoming webhook requests* | 500/minute |
*Applies to public (unauthenticated) requests sent to any workflow’s webhook URL, including web form submissions. The 500/minute allowance is platform-wide and shared by all public incoming webhook requests; it is not a separate allowance per workflow or per team, so a request can be throttled even when its own workflow receives fewer than 500 requests per minute. Requests that include a valid user key or bearer token are limited per user instead of counting against the shared allowance. Requests above the limit receive an HTTP 429 Too Many Requests response before a workflow instance is created or queued, so nothing appears in Catalytic for that request. The response includes a Retry-After header; clients should wait for that interval and send the request again.
Thanks for your feedback
We update the Help Center daily, so expect changes soon.
Link Copied
Paste this URL anywhere to link straight to the section.