Platform limits
How many buttons, actions, records, and messages a bot can handle, and what to do when a limit is reached.
Bu sayfada
If a reaction will not save or the bot processes only part of a list, it may have reached one of the limits below. For example, the bot can process up to 500 list items in one pass, but it can send no more than 50 messages in response to one event. To message more people, use a broadcast.
The first column shows each limit's technical name. You only need it to match a limit to an error message or set up an API connection. API limits are described separately.
Limit table
| Key | Value | Applies to | Limits |
|---|---|---|---|
trigger_keywords | 100 | Text trigger | Keywords in one trigger |
trigger_keyword_runes | 200 | Text trigger | Characters in one keyword |
for_each_items | 500 | Loop action | List items in one pass |
sends_per_reaction_run | 50 | Reaction run | Outgoing messages for one incoming event |
web_request_timeout_seconds | 120 | Web request | Request timeout in seconds |
web_request_connect_timeout_seconds | 30 | Web request | Connection timeout in seconds |
web_request_retry_count | 5 | Web request | Retries |
web_request_retry_pause_seconds | 60 | Web request | Seconds between retries |
test_user_ids | 20 | Bot settings | Test users |
sheets_read_rows | 5000 | Google Sheets action | Rows scanned by “last row” and “find row” |
people_export_rows | 10000 | People → CSV export | Rows in one export |
compute_expression_bytes | 4096 | Compute action | Bytes in an expression, condition, or decision-table value |
compute_formula_bytes | 16384 | Compute action | Bytes in an advanced formula |
compute_rules | 64 | Compute action | Rules in a decision table |
compute_formula_output_bytes | 4194304 | Compute action | Bytes in an advanced formula result |
compute_formula_steps | 500000 | Compute action | Steps in an advanced formula calculation |
record_query_rows | 10000 | Find records action | Rows in one collection query |
record_query_bytes | 16777216 | Find records action | Data bytes in one collection query |
pairup_items | 10000 | PAIRUP function | People in one pairing run |
utm_value_runes | 64 | Link to the bot | Characters in one UTM tag value |
block_attribution_hours | 24 | Broadcast report | Hours after delivery during which a block is attributed to the broadcast |
What happens when a limit is reached
- Keywords. A reaction with more than 100 keywords, or a keyword longer than 200 characters, cannot be saved. Split the words across several reactions. For a large list of words, you can use a collection and the “is in collection” condition.
- Loops and messages. A reaction that attempts to send more than 50 messages in response to one event cannot be saved. Use a broadcast to message many people.
- Web requests. A request with a timeout or retry setting above the limit cannot be saved.
- Test users. You can add no more than 20 user IDs in bot settings.
- Calculations. A Compute action whose formula or decision table exceeds a limit cannot be saved. Length is counted in bytes, so some characters take more space than the same number of English letters. Split a long calculation into several Compute actions and pass intermediate results between them. See Formulas.
- Reading Google Sheets. “Read last row” and “Find row by column value” scan at most 5000 rows in a sheet. If there are more rows, the bot shows
sheets_scan_limitinstead of incorrectly saying “not found.” Divide the data into several sheets, or use “Read rows” to read up to 500 rows at a time.
The values in this table are checked against the platform's current limits.