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 table’s SQL/Python errored during the build	Expand the error in the banner; a Data Admin can rebuild after the input problem is fixed — or ask Ronja to fix it in an exploration
Banner “Out of sync — showing data from last successful build”	An input changed and the table is stale; you’re seeing the last good data	A Data Admin rebuilds from the banner
“No data available. Build the table to see results.”	The table has never been built	Run the build (Data 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

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 has an approval gate — it can only run from a chat where an approver signs off	Run it through an exploration, or ask Ronja to remove the gate. Don’t schedule gated workflows — see automation triggers
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 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)

Full guide: Monitor runs and traces.

An automation didn’t run

Symptom	Likely cause	Fix
Row shows “Paused”	The automation is disabled — deleting its workspace 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
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 → Governance.”	The org-wide email ingest prefix hasn’t been set	An Admin sets it once at Organization → Governance
“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 an approval-gated workflow — gated workflows fail closed on automations	Point the automation at an ungated workflow or 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 (Data 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 data-admin role or membership in an admin workspace”	You tried to change a workspace- or organization-scoped resource without the required role	Propose the change instead (it becomes a draft/proposal for review), or ask a Data 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

Roles overview: the roles capability matrix.

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 Data 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, and text/code files	Convert to a supported format (e.g. export to CSV or PDF)
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.