Skip to content

How-to guide

Troubleshooting

What Nawa says, what it means, and what to do. Every turn also has a trace id (shown with an error, and in the receipts); keep it if you ask for help, since it names the exact run in Nawa's log.

"Nawa couldn't start"

Nawa's engine stopped while Nawa was starting. The window shows the error code and the log that holds the engine's own account of it, %APPDATA%\Nawa\data\server.log. Close Nawa and open it again; if it fails again, keep that log for your report.

"Model request failed"

The provider refused or did not answer a request. The card says the status it returned.

  • 401 or 403 — the key is wrong, expired, or lacks access to the model. Open the setup card and test the connection.
  • 429 — the provider is rate-limiting you. Nawa retries a few times on its own; wait, or choose a smaller model for the helper role.
  • 400 with a message about the request — the model rejected something Nawa sent. One known case, a provider that accepts only auto, none or required as the tool choice, is handled: Nawa remembers it for that deployment and asks again the accepted way. Anything else is worth reporting with the trace id.
  • No response, or a network error — the endpoint is unreachable: a local server that is not running, or a URL with the wrong port or path. Test the connection from the card. Nawa connects through the proxy Windows is set to use, PAC scripts included, and trusts the certificates Windows trusts, so a company proxy or an antivirus that inspects HTTPS works as it does in your browser; a SOCKS proxy, or one that asks you to sign in, does not.

The setup card says "Key missing"

No key is saved on that card. Paste one and test the connection. A card whose key was saved but whose model was never chosen says so instead; test the connection and choose the model.

The provider says the context is too large

The chat holds more than the model can read at once; the provider's own wording varies ("context size has been exceeded", "maximum context length"). Nawa compacts long chats on its own; if this still appears, the model's window is smaller than Nawa measured, or one message (a large attachment, a huge tool result) is bigger than the window. Start a new chat for the next task, or attach a smaller file. The composer's context gauge shows how full the window is.

The connector says "Needs authentication"

The server lists its tools but refuses to run them until you sign in. Press Sign in on its entry. If the sign-in page asks for a client ID, the service does not register clients on its own; the entry explains where to create one.

The decision model says "No Laya worker is loaded"

The Laya server answered that no model is loaded. Start the worker on the server (from its dashboard), then press Test connection again. "Nothing answered at …" means the server URL is wrong or the server is down.

Through OpenRouter, "Save a key on the OpenRouter card first." means the Jev card is set to use the OpenRouter card's key and that card has none.

A file tab says "… no longer exists in this workspace"

The drawer remembered a file from an earlier session that has since been deleted or rebuilt away. Close the tab; the chat's Files view shows what the workspace holds now.

A permission card keeps waiting

Nawa is paused until you choose. Cards never time out on their own; if you have left the chat, the card is still there, with the time it has waited. Choose, or press Stop generating (the send button while a turn runs) to end the turn.

The web is off

If Nawa answers from memory when you expected research, the web is off for this chat: turn the web toggle in the composer on. If the toggle is unavailable, no search key is saved — Settings → Web → Brave API key.

An app does not open in the drawer

The drawer runs one app at a time and stops the others; a tab whose app was stopped shows a dot and starts again when you show it. If an app fails to start, the menu on its card offers Open in External Browser and Open in Windows Explorer so you can see the files it built. If the drawer opened but stayed empty after an update, restart Nawa: the running engine and the renderer must be the same version.

Where to look further

  • The receipts in the transcript: every step's input, output and timing, including the model's own requests.
  • %APPDATA%\Nawa\data\server.log: the engine's log, one line per tool call and per turn, with [turn], [tool], [decisions] and [system-error] entries keyed by trace id.
  • %APPDATA%\Nawa\data\runtime\trace-index.jsonl: the timing of every phase of every turn, as one JSON line each.

Each log keeps its newest 5 MB. The 5 MB before them are in the same file with .1 added, such as server.log.1; older entries are deleted.