Troubleshooting

Find your symptom, check the likely cause, apply the fix. Exact product messages are quoted where they help you match what you’re seeing.

A table build failed

Symptom	Likely cause	Fix
Banner “Build failed” on the table page	The last build errored: its SQL or Python failed, or what the table asks for can’t be produced from its input tables (a column it needs isn’t there). Usually the table has never built successfully — but see the next row for the one case where it has	Expand the banner — it explains what stopped the build, naming the missing column or table. An Admin can rebuild once the input problem is fixed — or ask Ronja to fix it in an exploration
Banner “Build failed” saying an input table no longer exists — but the table still shows data	One of the table’s input tables was deleted. Every rebuild from now on fails the same way, so the table is flagged as broken rather than merely stale, even though its last good data is still there to query	An Admin restores the deleted input from Trash, or edits the table to point at a different input (or drop it). Restoring the input puts the table back in the rebuild queue on its own
Banner “Out of sync — showing data from last successful build”	The most recent build failed, so you’re seeing the last good data. Either an input changed, or the rebuild couldn’t produce the table from its inputs any more — an input that lost a column is the usual cause	Expand the banner to read why the rebuild failed, then have an Admin rebuild — or use Investigate with Ronja in the banner
“No data available. Build the table to see results.”	The table has never been built	Run the build (Admin), or push files then POST /build for file-fed tables
Table stuck on “Building table…”	A build is still running — larger tables build in pieces	Wait; the page updates live as the build progresses

More on statuses: table types.

A workflow run failed

Symptom	Likely cause	Fix
Run shows red “Failed”	The Python errored	Open the run: the Log tab has the full output (errors in red); the Steps tab shows exactly which step failed. Ask Ronja to fix the workflow in an exploration
Run succeeded but shows a yellow “degraded” badge	A best-effort step failed while the run completed	Open the Steps tab to find the failed step — decide whether it matters
“this workflow requires approval and cannot be run from this entry point”	The workflow carries a legacy Pre-run approval gate (labelled Deprecated on its page) — it can only run from a chat where an approver signs off	Run it through an exploration, or ask Ronja to convert it to a mid-run approval, which works from every entry point and keeps the same approvers — see Approval before a run
Run refused with a credits message	The organization’s wallet is empty — an empty wallet blocks workflow runs too	The Super Admin can buy credits on the Billing page
Run failed with “recursion depth exceeded” or a message about being too many chained runs deep	The chain of Agents starting workflows starting Agents went deeper than Ronja allows. Chains this long are nearly always an accidental loop	Ask Ronja to flatten the chain — start the Agent from the workflow that begins it rather than from one nested inside it. A previously-working pipeline can hit this the first time it runs after the limit began applying
Run failed with a message about the Agent needing to be started without waiting	The workflow waits for a Saved Agent that is set up to ask a person and wait for their reply — an Agent that stops to ask someone must be started and left to it	Ask Ronja to change the workflow so it starts the Agent and moves on instead of waiting. See Create a Saved Agent
Run times out around 10 minutes	The default execution window is 10 minutes	Ask Ronja to enable dedicated compute for the workflow (1-hour window, slower start)
Run failed at an approval step saying an approver isn’t a member of the organization	Every approver has to be somebody with a Ronja account in this organization. An address with no account behind it is refused at the step rather than mailed and never answered	Ask whoever built the workflow to name people who are members — “ask the finance team to approve before it posts” — or invite the person first. With nobody named at the step and no approvers set on the workflow itself to fall back on, the run fails at that step for the same reason
Run sits at Awaiting approval and nobody was emailed	The named approvers all left the organization between the moment the run asked and the moment the email went out	Open the run: the card names who it is waiting on. An Admin can always decide a run that is already waiting
Run failed right after the workflow was republished, while it was Awaiting approval	An approved run never continues on a new version of the workflow. Publishing an edit while a run waits ends that run rather than resuming it against code the approver never saw	Re-run it — the decision has to be made on a run that starts on the current version. Land workflow edits when nothing is waiting on a decision. See Mid-run approvals

Full guide: Monitor runs and traces.

An automation didn’t run

Symptom	Likely cause	Fix
Row shows “Paused”	The automation is disabled — deleting its access group also pauses it	Flip the toggle back on
Webhook calls return 429 “daily webhook run cap reached”	The 1,000 runs / 24 h quota is used	Wait for the rolling window, or reduce caller frequency
Table trigger stopped firing	The 50 runs / 24 h loop-safety cap was hit	Check what’s rebuilding the watched tables that often
A Mailbox automation shows off and nobody paused it	Its connected mailbox was disconnected. Ronja switches the automations watching it off rather than leaving them green against a mailbox that’s gone	Connect a mailbox again on the Mailboxes page, then point the automation at it: open the automation, pick the newly connected mailbox in its trigger, save, and switch it back on. A reconnected mailbox is a new mailbox even at the same address, so re-enabling alone is refused. Re-enabling starts from that moment, so mail from while it was off isn’t worked through
A Mailbox automation still reads Active but nothing fires	The mailbox itself has stopped working — its authorization needs reconnecting, or a check is failing. Unlike a disconnect, nothing is switched off and nothing is marked	Open the Mailboxes page and look at that mailbox’s card; Reconnect if it asks you to. The automation resumes on its own — there’s nothing to re-enable
A Mailbox automation didn’t fire on mail already sitting in the inbox	Only mail that arrives after you enable it counts. Enabling — or re-enabling after a pause — never replays a backlog	Ask Ronja to work through the backlog in an exploration. Nothing makes the trigger reach back
Mailbox runs stopped part-way through a busy day	The per-automation cap — 1,000 runs / 24 h, and 60 per minute — was reached	Wait for the rolling window, or narrow Filters (optional) so fewer messages fire it
Email trigger ignores messages	The sender isn’t on the allowlist (unlisted senders are dropped silently), or the routable address was rotated	Add the sender’s address or domain to the allowlist; re-copy the current routable address
“Address pending — set your org’s ingest prefix in Organization → Approvals.”	The org-wide email ingest prefix hasn’t been set	An Admin sets it once at Organization → Approvals
“job is already running” when clicking Run now	The previous run hasn’t finished	Wait for it to complete
Every fire fails at an approval gate	The action is a workflow with a legacy Pre-run approval gate — those fail closed on automations	Ask Ronja to convert it to a mid-run approval (which automates fine), or point the automation at another workflow or a Saved Agent — see Approval before a run

I answered Ronja and nothing happened

When a Saved Agent or automation pauses to ask a person something, the reply is picked up silently — and when a reply is not accepted, that is silent too. Ronja never writes back to say a reply was ignored, so the run simply keeps waiting.

Symptom	Likely cause	Fix
The run reports nobody answered, but the person is sure they replied	The reply came from a different address than the one Ronja asked — a personal account, or a forwarded copy answered by someone else	Reply from the exact address the question arrived at. Only that address counts
Same, and they replied from the right address	The reply was an out-of-office or other automatic reply, or had no readable text in it at all — an attachment with nothing typed above it, or a message whose formatting carried no text	Reply again with typed text in it. A reply that quotes the original is fine, whether or not there is text above the quote
Same, with real text, from the right address, and the question came from one of your own connected mailboxes	Their mail system couldn’t confirm the reply was genuinely from them. For questions sent from your own mailbox, Ronja reads the sender checks the receiving mail server ran and refuses a reply those checks don’t positively confirm — including one they couldn’t confirm either way	Ask your mail admin whether the sender’s domain publishes a sender-verification policy (they’ll know it as DMARC). Until it does, replies from that domain can’t be accepted for these questions, and the run waits out its full window. Questions sent from Ronja’s own address are unaffected — they’re accepted on the reply address alone
Same, and the reply was very long	Ronja reads about the first 8 KB of a reply — several pages — and says in the run when one was cut short	Reply again with the important part near the top, or a shorter answer
The run says it asked from your organization’s mailbox but can’t be answered	Ronja lost track of which mail thread the question went out in, so no reply can be matched back to the run	Nothing to fix — the run says so plainly and continues without the answer rather than claiming nobody was asked. Re-run it if the answer mattered
The run finished without asking anyone at all	A limit was hit: 5 questions per run, 10 questions to one person per day, or 50 paused runs across the organization	The run says what it was missing. Wait for the daily window, or check whether other runs are sitting paused — see Limits and retention
Ronja sent a closing message (“thanks, that’s all I needed”), the person replied to it, and nothing happened	A message that needs no answer ends the exchange — nothing is listening for what comes after it	Nothing to fix. When Ronja still needs something back she asks a follow-up question instead, which does wait for a reply — see Carrying on the conversation
The run says it couldn’t write back into a conversation it had already opened	The conversation ran out: 20 messages from Ronja, or 30 days since its last message. An Admin detaching the mailbox from the Agent or automation stops conversations that are already open too, as does narrowing the mailbox’s Compose recipients or the organization’s Agent email policy — and on Slack, the person leaving your organization	Nothing is sent, and the run carries on rather than starting an unrelated new message. If the exchange still matters, re-run it so it opens a fresh conversation

Full guide: Create a Saved Agent.

A connection sync fails

Symptom	Likely cause	Fix
Badge “Re-auth needed” / “Authorization expired. Please re-authorize this connection to resume syncing.”	The OAuth token expired or was revoked	Click Re-authorize on the connection page (Admin)
“connection is disabled”	The connection’s toggle is off	Re-enable it, then Sync
“connection is already syncing”	A sync is in flight	Wait, or Stop the current sync first
“connection config is incomplete — check your settings” (or “select a database and tables”, “select at least one file or folder to sync”, …)	No tables, datasets, or files have been selected yet — no data is fetched until at least one is	Open the connection and complete the dataset/table selection
Red error banner on the connection page	The last sync failed; the banner shows the source system’s error verbatim	Fix the upstream issue (credentials, network, permissions) and Sync again — or ask Ronja for help in an exploration
Schedule won’t save	Schedules can’t fire more than once per hour	Pick an hourly-or-slower cadence

Full guide: Connect a data source and Fix data issues.

Permission denied

Symptom	Likely cause	Fix
“You don’t have access to this exploration.”	The exploration wasn’t shared with you	“Ask the owner to share it with you.”
“Build mode is disabled for your account. Contact an administrator to request access.”	Build access is off for your role/user	An admin enables it in Control Center → Build access
“You have reached your monthly credit allocation. Contact an administrator to raise your limit.”	Your personal monthly credit cap is used up	An admin raises your allocation in Control Center → Allocations
“Your account has been blocked from running AI turns. Contact an administrator.”	An admin set your allocation to Blocked	An admin unblocks you
Errors like “…requires admin role”	You tried to change an organization-scoped resource without the required role	Propose the change instead (it becomes a draft/proposal for review), or ask an Admin
API call returns 403 forbidden	The token’s role is too low, or a scoped token lacks the needed grant	Use a token with the right role and scope — see the API reference
You can’t approve a request you made	Proposers never approve their own proposals; self-approval may also be disallowed org-wide	A different admin reviews it
A link Ronja sent you stops on Couldn’t check your organizations	Not an access problem: the link belongs to a particular organization, and the list of the ones you’re a member of didn’t load, so Ronja can’t tell whether it’s yours	Click Try again; or Continue in the organization you’re already in to open the page there anyway

Roles overview: the roles capability matrix.

Missing pages or menu entries

Most “missing” navigation is role-gating, not a bug:

What’s missing	Who sees it
The Admin sidebar entry (and everything under it)	Admins and Super Admins only
Organization (login domains, danger zone)	Super Admin only
Usage and Control Center	Admins whose organization has billing access enabled — ask Ronja to enable it
Billing (buy credits)	Super Admin only
Connections page content	The connection list requires Admin — below that role the page shows no connections
The Build segment on the exploration start screen	Users granted Build access in the Control Center
The model/effort picker in chat	Users with the capability, in an organization with a funded credit wallet (hidden during a downshift)

Ronja doesn’t reply in Slack or Teams

These fixes cover bridged Slack and Microsoft Teams channels alike.

Symptom	Likely cause	Fix
No reply to a channel message	The bridge’s trigger is @mention (the default) or the keyword “ronja”, and the message matched neither	@-mention Ronja — once she owns a thread, follow-ups there don’t need it. An admin can change the trigger on the bridge page
“You don’t have a Ronja account yet — ask your admin to add you to Ronja, then try again.”	Your Slack email doesn’t match a Ronja account in this organization	An admin invites you (or approves your access request); your next message auto-links
“your Ronja account is in a different organization than this Slack bridge”	Your account lives in another Ronja organization	Ask your admin to sort out which organization the bridge should serve
“Your Slack identity is already linked to a different Ronja account.”	A stale identity link	“Ask your admin to reconcile this.”
Bridge status “Needs reauth”	The Slack/Teams authorization expired or was revoked	An admin clicks Reauthorize on the Bridges page
Bridge status “Disconnected”	Ronja can no longer post, or the bridge was disconnected — disconnecting now removes her from the channel	Re-invite @Ronja from Slack, or an admin reconnects from the bridge’s page
No bridge in this channel	No Slack channel — public or private — is connected automatically; the bot must be added deliberately	/invite @Ronja in the channel, or use Add bridge on the Bridges page. If Admin-only connections is on, a Ronja admin has to do it
Teams: no answer in a channel	Teams channel messages require an @-mention; private Teams channels and group chats aren’t supported	@-mention Ronja, or DM her

Full guide: Use Ronja in Slack and Teams.

An upload was rejected

Symptom	Likely cause	Fix
“Image {name} exceeds 20 MB limit”	Images are capped at 20 MB	Resize or compress the image
“Document {name} exceeds 100 MB limit”	Documents are capped at 100 MB	Split the document
“Text file {name} exceeds 5 MB limit”	Text files are capped at 5 MB	Trim it — and note only ~50 KB reaches Ronja anyway; consider uploading data as CSV/Excel instead
A file type won’t attach	The chat accepts data files, images, documents, text/code files, and zip archives	Convert to a supported format (e.g. export to CSV or PDF)
A zip attached but its files didn’t appear	The archive is over the automatic-unpacking budget — 25 files, 150 MB, or 10 images — so Ronja listed its contents instead of unpacking a partial subset	Ask her to unpack it: “unpack all of them”, or name the files you need. See Zip archives
Ronja says a zip is password-protected	Encrypted archives can be listed but not opened	Send the password, or re-send the files unencrypted
“too many members to list” on a zip	A zip is only listed up to 10,000 members; past that Ronja won’t read its contents list at all	Send the specific files you need, or a smaller archive — see Zip archives
Ronja unpacked only some of a zip	An unpack request can return short — the working-log step reads “12 of 40 extracted”	Ask her to unpack the rest, and don’t rely on a total computed before it completes
File push API: 400 “invalid filename” or “not a valid parquet file”	The push API accepts only .parquet files with clean names	Convert to Parquet first — see the API reference
File push API: 413 “file too large”	1 GiB per-file cap	Split the file into several Parquet files — they build together

All caps in one place: Limits and retention.