The consolidated limits table. Values come from the product as audited — if something isn’t listed here, it isn’t documented as a limit.
| What |
Window |
| Trash (access groups, features, tables, workflows, notes, secrets, MCP servers, apps, connections, automations, Saved Agents) |
30 days, then permanently purged |
| Trash page listing |
Most recent 100 items per section |
| Organization deletion cooling-off |
7 days — contact Ronja support to restore before then |
| Execution-trace detail |
Kept ~360 days after the run started. A workflow that pauses and continues keeps ONE trace for the whole pipeline, so the clock runs from the first run of the chain |
| A workflow that keeps pausing |
Given up on after ~11 months from the first run of the chain, with a message saying so. Work that needs to keep going longer belongs in an automation on a schedule |
| A decided (or expired) run-approval request |
Kept 90 days, then deleted — the run itself and its trace keep their own windows |
| Connected-mailbox chat read history |
Cleared 7 days after a chat reads a mailbox thread |
| Connected-mailbox search by an automation, when no age is given |
Looks back 7 days — Ronja can search further back when she needs to. Searching a mailbox yourself in a conversation is not limited |
| Activity Overview usage ledgers (processing counts, popular tables, app opens, per-user queries/runs) |
Cover at most the last 90 days |
| Login-domain verification link |
Valid 72 hours |
| What |
Limit |
| Images (PNG, JPEG, GIF, WebP) |
20 MB per file |
| Documents (PDF, DOCX, PPTX, …) |
100 MB per file |
| Text and code files |
5 MB per file — only the first ~50 KB is sent to Ronja (a “truncated” badge appears) |
| Data files (CSV, TSV, XLSX, XLS, Parquet) |
No fixed size cap in the picker |
| Files attached to a single message |
50 in the app — chat attachments, and a drop onto the home page. Over Slack or Teams, 10 per message; anything beyond that is skipped and Ronja names the files she couldn’t take |
| Zip unpacked automatically |
Up to 25 files, 150 MB of contents, and 10 images — a bigger archive is listed instead of unpacked, and unpacked on request (Zip archives) |
| Zip unpacked on request |
200 files and 1 GB per request — ask again for the rest |
| What |
Limit |
| File push API |
Parquet only · 1 GiB per file |
| Connection sync cadence |
Minimum once per hour; interval mode up to 8,760 hours |
| Feature export |
512 MiB per table · 4 GiB per export — over-cap tables export metadata only |
| What |
Limit |
| Favorites |
10 per type — “Max 10 favorites — unfavorite one to add another” |
| Sidebar exploration lists |
Your last 50 + the last 50 shared with you |
| Prompt queue |
One queued prompt at a time; attachments can’t be queued |
| Tangent fork point |
Can’t branch from very old points — roughly 5,000 messages back (“this point is too far back to branch from”) |
| Tangent return summary |
100 KB |
| “Add to chat” text selection |
2,000 characters |
| Personal memory |
2,000 characters |
| Search (⌘K) |
Minimum 2 characters; up to 40 results shown |
| What |
Limit |
| Workflow run timeout |
10 minutes by default; 1 hour on dedicated compute (which can take up to ~90 s to start) |
| Function return value shown inline |
8 KB |
| Spawned agents listed per run |
200 (shown as “200+” past the cap) |
| Run starts from one workflow run |
60 at once, then 5 per second as the allowance builds back up — shared budget: starting a Saved Agent and starting another workflow both count. A batch of parallel starts fits inside the burst, so an ordinary fan-out is not torn in half |
| Saved Agent runs at once, per organization |
60. An admin can change this for your organization |
| How far ahead a run may pause |
1 year. A Durable workflow that asks to wait until a moment further out than that is refused when it tries to pause |
| How long a Waiting run stays paused |
14 days past the moment it was due to continue. A Durable workflow that pauses and cannot be woken by then is failed, with a message saying why |
| How long a run stays Awaiting approval |
7 days by default; the workflow’s author can set anything up to 14 days. Nobody decides by then and the request expires and the run fails — see Monitor runs and traces |
| How long an agent waits at one go |
24 hours. An agent that asks to wait longer is refused and told to use an automation instead |
| How many times one agent run may wait |
5. Past that it is told to finish with what it has, or to set up an automation |
| How long an agent run may live in total |
72 hours from when it started, waiting included |
| What |
Limit |
| Agent chain depth |
3 generations when one agent runs another directly; 6 when the chain goes through workflows. Past it the run is refused with an explanation |
| Agent runs at once |
20 per organization — further starts are refused until in-flight runs finish (an admin can raise this for your organization) |
| Paused runs |
50 per organization, counted across both kinds of pause together — runs waiting for someone’s reply and runs waiting on a timer or another run. Past that, an agent that would have paused finishes with what it has and says what was missing instead |
| How long a run waits for a reply |
3 days by default, between 1 and 14 days if the Agent sets its own — then the run continues without an answer |
| Questions one run may ask |
5. Past that the run carries on without asking again |
| Questions to one person per day |
10 per person per organization (rolling 24 h). Past that the agent is told to try tomorrow or ask someone else |
| How much of a reply Ronja reads |
8 KB — several pages of text. A longer reply is read up to that point and the run is told plainly that the rest was cut, so a fragment is never mistaken for the whole answer |
| Files sent with a question |
10 files, 25 MB total. Email only — a question asked over Slack cannot carry files and is refused if it tries. From an Outlook mailbox the ceiling is about 3 MB per message (Microsoft’s limit); an oversized send is refused before anything goes out |
| Messages Ronja can send in one conversation |
20 — the first question, every follow-up, and every closing message together (the person’s own replies don’t count). Past that the run carries on without contacting them again |
| How long a conversation stays open |
30 days after its most recent message, pushed out again by each new one. Continuing a conversation works for questions sent from a connected mailbox and for questions asked over Slack; one sent from Ronja’s own address gets one answer and stops there |
| Questions open in one conversation |
One at a time |
| How long a closed conversation is kept |
7 days after it stops being open, then Ronja’s record of the conversation is deleted. A conversation still waiting on an answer is never deleted |
| What |
Limit |
| Schedule trigger |
Minimum interval 1 hour |
| Webhook trigger |
1,000 runs per rolling 24 h · 1 MB request body · signed requests within a 5-minute window |
| Table trigger |
50 runs per rolling 24 h · at most 25 watched tables |
| Event trigger |
5,000 runs per rolling 24 h across all event automations (per-organization loop-safety ceiling) |
| Mailbox trigger |
Filters are optional; at most 50 entries per filter list. Only mail arriving after the automation is enabled is picked up, and mail is looked back over a few hours only |
| Automation rate limit (webhook, email, event & mailbox) |
Per-automation two-window throttle — system defaults 60 runs/minute and 1,000 runs/day; an admin sets the per-organization default and a max ceiling on the Automation limits page in the sidebar’s Billing & Control group (Admin only) |
| Email trigger |
Chained automation depth capped at 4 |
| Address / URL rotation |
About once per minute |
| Declared resource references per automation |
200 |
| What |
Limit |
| Email recipients Ronja can send to from her own address |
500 per organization per day (rolling 24 h) |
| Email recipients Ronja can send to as a connected mailbox |
500 per mailbox per day (rolling 24 h) by default — an Admin sets a Daily send limit on the mailbox card, up to 10,000 |
| Recipients on one email |
20, counting the main recipients and anyone copied in (Cc) together |
The split is by which address the mail came from. Everything Ronja sends as one of your connected mailboxes — a reply in a chat, a reply or new email from an Automation or Saved Agent, a question she emails, and mail a workflow sends — draws on that mailbox’s own Daily send limit, and never on the organization-wide cap. Everything she sends from Ronja’s own address draws on the organization-wide cap, and never on a mailbox’s limit.
So the Daily send limit on a mailbox card is the whole answer to “how much mail can leave this address in a day”, whoever or whatever asked for it. Each connected mailbox has its own budget, independent of the others and of the organization-wide cap.
All of these count recipients, not messages: one email to ten people counts as ten. People copied in (Cc) are recipients like any other: they go through your organization’s email policy and count toward whichever budget applies. There is no Bcc — see Copying people in.
Questions to a person count too, when they go out as email. A question an Agent emails is a recipient like any other and goes through your organization’s email policy. Which budget it draws from follows the same rule as everything else: a question sent from a connected mailbox draws one from that mailbox’s Daily send limit, and a question sent from Ronja’s own address draws one from the organization-wide cap. It also has its own, much tighter limits on top (5 questions per run, 10 questions to one person per day, 50 paused runs per organization) — see Saved Agent runs above. Every later email in the same conversation — a follow-up question, or a closing message that needs no answer — is a recipient again and draws from whichever budget applies. A question asked as a Slack message is not email and touches neither the policy nor either budget.
| What |
Limit |
| Source files |
5 MiB per file · 100 files per app · 50 MiB total |
| Allowed tables / secrets / agents / workflows |
25 each |
| Query results |
1,000 rows by default; hard cap 100,000 |
| Query rate |
60 queries/second, with a burst allowance of 600. Unused allowance builds back up continuously, so an app that loads many panels at once is fine — only a runaway loop sustains enough traffic to be throttled. A throttled call is retried automatically before your app ever sees it |
| External database query timeout |
60 s |
| Server-side fetch proxy |
10 MiB request/response · 30 s timeout |
| Version history |
Up to 100 snapshots |
| Viewer session token |
1 hour (refreshes automatically) |
| What |
Limit |
| Tags per resource |
20 |
| Tags per organization |
500 distinct tags |
| Tag name length |
64 characters |
| What |
Limit |
| Open move requests |
100 per user |
| Request notes, decision reasons, move rationales |
4,000 characters each |
| Table / app drafts |
One open draft per person per resource |
| What |
Limit |
| Notification email recipients |
47 |
| Role changes taking effect on active sessions |
Up to ~2 minutes |
