Automation Limits

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:

• There's a 60 second timeout limit for automations.
• There's a limit of 720 automation runs per minute and 3600 automation runs per hour.
• There's a limit of 10 emails per minute.
• There's a limit of 10 SMS per minute.
• There's a limit of 3 automation test runs per minute.
• 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.

In addition, an automation run will time out after a minute. 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".