To ensure that your automation has failsafes in case you may have misconfigured your logic, we've implemented limits to protect any accidental issues.
Limit Details
The following limits to automations are per workspace:
| Limit | |
|---|---|
| Automation timeout | 60 second |
| Automation runs | 720 runs per minute 3600 runs per hour |
| Automation test runs | 3 test runs per minute |
| Actions on tables and connector functions (API Calls) | 1,200 total API calls per minute |
| Concurrent automation runs | Up to 10 automations are guaranteed to run at a time as of r283/LTS13, though the number can be higher. If the limit is reached and another automation run begins, it will be queued, delayed, and attempted to re-run after a certain amount of time. After a certain number of re-runs, the automation will be dropped from the queue and listed as limited. |
| Emails sent | Maximum 10 sent per minute |
| SMS sent | Maximum 10 messages sent per minute |
| Self-triggering automations (i.e. an automation that fires off of an "update table record" and updates that same table record) | 25 calls off of one triggering event. Read more here on how to mitigate this issue. |
Limit Reached
When an automation run limit is hit, any subsequent automation run will listed as limited but not run.
Automation Example
For example, if I have six automations that responds to an "Add Table Record" event, one of those automations will have an automation run that responds with "limited".