When Axi can't finish, it tells you

A turn that went wrong used to end in silence: the Thinking line vanished, the answer stopped mid-sentence, and there was nothing to say whether Axi had finished or fallen over. Now it says so, and the conversation is left in a state you can act on.

The reason, in plain language

A failed turn now writes a notice under the conversation — the AI provider is unavailable, the connection to Axi was lost, too many requests right now — in your language, instead of a raw provider string or nothing at all. The technical detail is still there for support, folded behind Technical details.

This works whether or not your tab was open when it happened. Axi keeps working after you navigate away, so a turn that fails while you're elsewhere has its notice waiting in the conversation when you come back.

Nothing is lost, and nothing is repeated

Axi builds as it goes, so a turn can fail after it has already made two widgets. Those widgets, and the part of the answer that got written, are kept — in the dashboard and in the conversation, so reopening the thread later shows exactly where it stopped.

That is also why Retry is offered carefully. It re-runs the turn when re-running is safe; if Axi had already created or changed something, the button is withheld and the notice says why, because a replay would do it twice. Ask for the next step in your own words instead.

Queued messages wait their turn

Lining up prompts while Axi works is unchanged — except that when a turn fails, the ones behind it no longer vanish or fire into the same failure. They stay listed, and go out once you retry or dismiss the notice. You can remove any of them first.

📖 When a conversation doesn't finish · When an Axi run fails