When “Bot failed to respond” needs a backend recovery

Every message can fail with Bot failed to respond / Something went wrong while generating the reply. Try again — including a plain hello — while the Agent Computer screen is still visible. Then Reset Agent Computer fails with Reset failed… may be in a partial state. Staff on Bot failed to respond; Reset stuck in partial state put that class on the Agent Computer backend, not on your local setup.

Confirm the class

1. Failed-to-respond hits simple chat, not only computer-use tasks.
2. The Agent Computer pane still shows a desktop (a blank local crash looks different).
3. Reset (or Update) fails and mentions a partial state.
4. Retrying Reset / Update from the client does not finish.

Same class when Create Bot sticks on a translating “Creando…” (or equivalent) screen with failed-to-respond while the Agent Computer is still visible — reported on Windows 0.44.0 in Cannot create bot stuck on Creando + failed to respond. A visible computer pane does not prove generation can finish.

Same class on 0.44.0 Windows when bots die after Reset and Recover/Update fail while users ask staff for a backend recover (Agent computer stuck after Reset). Keep the same rule: stop stacking Reset; ask for backend recovery and wait.

Usage exhaustion and load rejection are different: Understand Grok Bot usage and “failed to respond”. Client Update/Recover/Reset all failing on a dead computer is another path: When client Update, Recover, and Reset all fail. First-Bot create failures without a backend partial-state message: When Android cannot create the first Bot.

What staff told users to do

1. Stop clicking Reset and Update.
2. Do not reinstall the app.
3. Do not log out while recovery is in progress (staff: that can make recovery harder).
4. Open Send Feedback (or the forum) and ask for a manual backend recovery. Say you want bots, chats, and files kept.
5. Wait for staff to finish on their side before you touch Reset again.

On that thread, staff said bots, chats, and files were safe, and that Reset/Update could not finish because the computer was stuck in an in-between backend state.

Related partial-state UI

If you already hit “Reset failed… partial state” with a first-run Create-your-first-Bot screen, also read Fix Grok Bot after a failed Reset leaves a partial state. The rule is the same: do not stack another Reset while the first job may still be stuck.

Pitfalls

• Hammering Reset does not clear a backend partial state.
• A healthy-looking computer pane does not mean chat generation can finish.
• Collect version, OS, exact error text, Bot name, and approximate time/timezone before you file.