Chat errors appear below the composer as a code and a message. A turn that failed before the assistant ran any tool changed nothing and is safe to retry. A turn that failed after a tool had already run may have taken that action — check the Stream or the Workbench before you ask again.
The four codes
| Code | What it means | What to do |
|---|---|---|
busy | A turn is already running in this chat. | Wait for it to finish, then ask again. |
brain_timeout | The assistant took too long to answer. | Retry. |
brain_failed | The turn failed before it could complete. | Retry; if it keeps failing, contact support. |
network | Your browser could not reach Deloosh. | Check your connection, then retry. |
A turn that ends in an error also shows in the timeline as “This chat turn failed.” so the failure stays in the record rather than vanishing.
Did anything happen before it failed?
A chat turn is not all-or-nothing. The assistant answers by calling tools, and a turn can fail after one of those tools has already run and taken effect — the tool completes, and the turn then times out or errors on a later step.
So the question to ask about a failed turn is not “did it succeed?” but “did it get anything done before it stopped?”:
- It failed before running any tool — nothing happened. Retry freely.
- It had already run a tool — that action may have taken effect, even though the turn shows as failed.
The turn itself tells you which case you are in. Each tool the assistant runs appears as a chip on the turn, with a green dot once that tool has completed. A failed turn showing a completed tool chip is a turn that did something.
Retrying starts a new turn — it does not resume the failed one. If the first turn’s tool already landed a change, retrying can apply it a second time: a second draft, a second send plan, a second snooze. Deloosh does not automatically undo or de-duplicate the work of a failed turn.
When a tool has run, check before retrying. Open the Operator Stream to see what was recorded, or look at the Workbench for anything new. Reading is always safe — it never changes anything.
One thing a failed turn can never do is send email: the assistant has no send tool at all. A duplicate here costs you a redundant draft or plan, not a duplicate email to your audience. See CHAT-2, What the assistant will never do.
busy is a guardrail, not a queue
Deloosh runs one turn at a time in a chat. Asking again while a turn is in flight returns busy rather than stacking a second request behind the first — two turns acting on the same workspace at once is exactly how you get a contradictory result.
If you want to work on something else while a long turn runs, open a New chat from the sidebar.
When the chat itself is gone
If a chat you had open is no longer available, Deloosh says so — “That chat is no longer available. Showing the next available chat.” — and moves you to the next one. Your other chats and your workspace are unaffected.
Errors elsewhere in the workspace
These four codes cover the chat turn. Other views report their own failures in place — the Stream and Vitals views each say when they cannot load, rather than showing you stale or invented figures. See OS-3, The Stream: your decision timeline.
If you were signed out instead, see GS-4, Why was I signed out?.