---
title: "Automation limits"
slug: "automation-limits"
updated: 2026-04-09T21:03:57Z
published: 2026-04-09T21:03:57Z
canonical: "support.tulip.co/automation-limits"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.tulip.co/llms.txt
> Use this file to discover all available pages before exploring further.

# 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

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. |
| 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](https://support.tulip.co/r230/docs/looping-warning-in-automations) on how to mitigate this issue. |
| Variables per automation | 30 variables |

### Limit Reached

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 10 re-attempts, the automation will be dropped from the queue and listed as limited.

### Automation Example

For example, if I have eleven automations that responds to an "Add Table Record" event, one of those automations will have an automation run that responds with "limited".