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
There are limits to automations on a per workspace basis - listed here:
| Item | Limit |
|---|---|
| Automation timeout | There's a 60 second timeout limit for automations. |
| Automation Runs per Minute | There's a limit of 720 automation runs per minute. |
| Automation Runs per Hour | There's a limit of 3600 automation runs per hour. |
| Automation Test Runs per Minute | There's a limit of 3 automation test runs per minute. |
| Actions on Tables & Connector Functions (Total Number of API Calls) | 1,200 total API calls per Minute per Workspace |
| Concurrent Automation Runs | As of r283/LTS13, up to 10 automations are guaranteed to run at a time per workspace, 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 per Minute | Maximum 10 emails sent per minute. |
| SMS Sent per Minute | Maximum 10 SMS messages sent per minute. |
| Self-Triggering Automations | An automation that triggers itself(i.e. an automation that fires off of an "update table record" and updates that same table record) is limited to 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".