Limits
The fixed limits on agent calls, approval requests, input size and stored history, and the error each one returns.
The limits are on by default and fixed. They keep one connection from flooding the application and keep each call inside Convex's own limits. An agent that reaches one gets a code and a message that says what to do.
| Limit | Value | When reached |
|---|---|---|
| Writes per agent connection | 60 a minute | RATE_LIMITED; the message says how many seconds to wait |
| Open approval requests per agent | 20 | RATE_LIMITED; the agent waits until people decide |
| IDs in the input of one call | 1,000 | TOO_LARGE, before the handler runs |
| Rows one approval request covers | 500 | TOO_LARGE; ask for fewer at once |
| Size of one approval request | 256 KiB, with its plan and input | TOO_LARGE; make the plan smaller, or split the work |
| Time to decide an approval request | 30 minutes | APPROVAL_EXPIRED; the agent asks again |
| Items per page of a tool | 1 to 100, 50 by default | larger values are cut to 100 |
| Size of one MCP request | 64 KiB | HTTP 413, before any tool runs |
| Rows in one activity list | 1 to 200, 50 by default | larger values are cut to 200 |
| Stored result of a write, for replay | 64 KiB | stored as { truncated: true, bytes }; the write itself is kept |
| Activity rows | kept 1 year | deleted by housekeeping |
| Decided approval requests | kept 90 days | deleted by housekeeping; the activity row records the decision |
| Finished in-app agent runs | kept 30 days, with their messages | deleted by housekeeping |
| Length of a tool name | 1 to 64 letters, digits, _ or - | error when the module loads |
| Text of an approval summary | one line, 300 characters | longer text is cut |
| Unclaimed upload links and files | 100 per agent connection | RATE_LIMITED; see Files from agents |
Read tools have no rate limit. Convex's own limits apply to them, and a page reads at most 100 rows.
A refused call does not count against a limit: its transaction rolls back.
Agents use the same limiter as the policy's limits: a bucket that refills continuously, not a fixed window.
Retries
A host may send a write twice, for example after a timeout. Give the call a
request_id. The same request_id with the same input returns the first
result; the write runs once. A request_id reused for a different call fails
with REQUEST_ID_REUSED.
The same call while its approval request is open returns the same request.
After the person declines, the same call gets APPROVAL_DECLINED, with or
without its request_id, until the declined request would have expired (30
minutes after it was made).
Known gaps
- A parent tenant does not see the open requests of the tenants below it. List them for each child tenant.