Error messages explained

Find the exact message you saw, in your own words, in the left column. The middle column says what it means; the right column takes you to the page with the full fix.

What it is

Most of Omniscio's errors are written as a plain sentence on purpose. This page is the index of those sentences: every row quotes the message verbatim — the words you actually see — so it can be found by reading down the page or by searching for any part of it.

If your message is not here, Something's not working? Start here routes by symptom instead, and Ask Omniscio can search the whole library.

Where to find it

The messages themselves appear where they happen: the first-run setup window, a dialog at launch, a notice on a session card, or a line in the conversation when a session stops. This page is the lookup that covers all of them, and it lives in the help library — open it on the help site, or paste any part of the message into Ask Omniscio and it lands here.

How it behaves

Install, first run, and the app's own tooling

The message you see	What it means	What to do
Repair Needed — "{App} is missing a required Windows runtime."	The Microsoft Visual C++ Runtime one of the app's native components needs is missing from this install.	Click Repair now in that dialog — Omniscio downloads and installs it from Microsoft itself. Details: First-time setup.
Claude Code isn't installed (or can't be found).	Omniscio cannot find the Claude Code command-line tool, so no session can start.	Install it with one click in Settings → Connected Tools, or set its path in Settings → General → Claude CLI Location. Details: First-time setup.
This step hit a snag	A step of first-run setup failed (usually a network or permission problem during that step).	The setup screen offers Try again; if it repeats, see First-time setup.
Temporary launch hiccup — retrying (1/3)…	The very first start of a session failed in a way Omniscio expects to be transient. It is already retrying on its own.	Usually nothing — it clears by itself. If it keeps counting up, see Couldn't launch the session below.
Update Needed — "{App} needs to rebuild a component for this version before it can start."	A core component (the database engine) was built for a different version. Your data is safe — this is not a database problem.	Follow the dialog: reinstall or update the app to the latest build. Details: App Update Notifications.
{App} update is ready — it installs the next time you restart.	A downloaded update is staged.	Restart when convenient. Details: App Update Notifications.

Signing in and accounts

The message you see	What it means	What to do
That email and password don't match an account.	The sign-in was refused — the pair does not match any Omniscio account.	Re-type the email and password; use Forgot password if needed. Accounts are separate from your Claude accounts: Add a Claude account.
This account has been disabled. Contact support if that seems wrong.	The Omniscio account is disabled.	Use the support route in the app (a session can file it for you) — see Bug Report Intake.
Too many attempts. Wait a few minutes and try again.	Too many sign-in tries in a short window.	Wait a few minutes; the limit clears by itself.
Login rate-limited by Cloudflare.	Cloudflare temporarily blocked the token endpoint during Claude sign-in. Your browser sign-in worked — only the token exchange was blocked.	Wait 15–30 minutes, then sign in again. Details: Auth pathways.
Authentication failed / Can't start sessions — sign in again	A Claude account's saved sign-in has expired or been revoked.	Omniscio can usually sign it back in for you: Sign accounts back in automatically.

Plan, billing, and limits

The message you see	What it means	What to do
You've reached your plan's project limit. Upgrade to add more projects.	Your plan allows a fixed number of projects and every slot is used.	Archive a project you no longer need, or upgrade. Details: Plan & Usage.
Could not start checkout. Please try again.	The payment page could not be opened.	Try again in a moment; if it repeats, check your connection. Details: Plan & Usage.
Paying account out of credit	The paying account behind a session or provider ran out of credit.	Top up in Plan & Usage; provider balances are listed under API Keys. See also Stripe credit top-ups.

Sessions

The message you see	What it means	What to do
Couldn't launch the session — the rest of the sentence names the reason (binary path, permission denied, disk full, or "please try again")	The Claude Code process could not be started. Each variant names one cause.	Fix the cause named in the sentence — the path in Settings → General, the folder's permissions, or free disk space. Details: Session stuck in "needs you".
Claude Code stopped unexpectedly before it could reply — it crashed (exit code 1).	The session's process died before producing any answer. The sentence says whether it crashed, was shut down, or simply exited, and carries a reference.	Click Retry. If it repeats, Session started but produced no output covers the checks in order.
Session timed out — Claude Code produced no output after N seconds, so it was stopped.	The session started but produced nothing before the time limit; the line names the engine, model, account and a reference.	Send a message to try it again; if it keeps happening, Session started but produced no output.
Session stalled — no output for N seconds, and automatic continuation is off.	The session went quiet and Omniscio will not nudge it while Auto-continue is off.	Send it a message to restart it, or turn on Auto-continue in Settings → Sessions. Details: Auto-restart stuck sessions.
Session stalled — no output for N seconds after N automatic continue attempts	Omniscio nudged the session the maximum number of times and it still did not answer.	Send it a message to restart it. Details: Context stall recovery.
This reply was cut off — the Claude Code process ended before it finished (with exit code N).	The process died mid-reply; the partial answer is kept.	Click Retry to pick the turn up again. Details: Aborted-response recovery.
User denied this action	A permission prompt was declined (often by mistake, or by a permission rule).	Re-run the step and approve it, or change the permission level. Details: Agent permission level.
Session stopped — this turn ran for over N hours without finishing	A single turn hit the absolute time limit and was ended automatically.	Send a new message to continue, or raise the limit in Settings. Details: Stuck sessions.

Data, sync, and memory

The message you see	What it means	What to do
The database is busy right now. Please try again.	Another part of the app was writing at the same instant and the write was refused rather than risked.	Retry the action. If it repeats for minutes, see Database compaction and Data folder recovery.
Cross-Device Sync is failing	The encrypted cross-device sync has failed repeatedly, so changes are not reaching your other devices.	Open the card for the failing direction and retry; details in Cross-Device Sync.
Low on working memory	Omniscio's memory use crossed the danger line and it captured a heap snapshot to explain why.	Close idle sessions or restart the app; details in Heap snapshot diagnostics.
Your local database reported a problem	A routine health check found a problem with the file that stores your sessions, messages and settings.	Make a fresh backup under Settings → Backup & Restore now, or restore an earlier healthy one. Details: Data folder recovery.
Database Error — "{App} could not open its database."	The app could not open its data file at startup (usually a sync client or antivirus holding it).	Do not reinstall. Follow Data folder recovery.

Integrations and automations

The message you see	What it means	What to do
An automation action permanently failed / Some automation actions could not be completed	An outbound automation action (a message, a webhook) failed after every retry. The card names the automations involved.	Open Automations (the card's button) and review or turn off the failing rule. Details: Automations & Auto-replies.
Gmail is disconnected	The Google grant expired or was revoked, so mail features stop updating.	Use the card's reconnect button. Details: Google Integrations.
Telegram is disconnected	Omniscio lost its Telegram connection and automatic reconnection has been failing.	Check your network, or reconnect Telegram from Settings. Details: Telegram integration.