Fix problems
Grok Bot not responding or "failed to respond": the recovery order
By Tal Slavin · Last checked · Next review 2026-11-06
Grok Bot not responding or "failed to respond": the recovery order
Bots gone silent, one Bot that always fails, or a computer shown offline: the recovery order, and when not to reset.
◈Key Takeaways (5)
- •A silent Bot is waiting on you, on an unhealthy shared computer, hit by an outage or out of usage.
- •Check status and look for a waiting card before touching the computer.
- •Order: resend, quit and reopen, check usage, update, Recover or Update Bot's Computer, Reset last.
- •One Bot failing while others work is often a safety filter on its history.
- •Never Reset during an open incident.
☰On this page (5 sections)
A Bot that is silent or shows "Bot failed to respond" is one of four things: waiting on you, on a stuck shared computer, caught in an outage, or out of usage. Work through the steps below and stop as soon as it answers.
Recovery order#
- Check status. If an incident is open, wait for Resolved, then resend.
- Resend the message, or use Resend on the failed one. If you see "rate limited" or "model provider is overloaded", wait a moment first.
- Look for a waiting card: an approval, question, sign-in or secret request. Answer it, or switch to another Bot and back to refresh.
- Quit fully and reopen the app (Quit from the menu bar or tray, not just closing the window).
- Check Weekly usage in Settings. At 100 percent with on-demand off or spent, that is the cause; see usage limits.
- Settings, Updates: install an app update, then Settings, Computer, Update Bot's Computer.
- Recover computer when the unreachable dialog offers it. It keeps durable files and logins.
- Reset Bot's Computer last. It restores the last saved snapshot, can lose recent unsynced work and removes installed apps and packages.
Do not Reset while an incident is open or while staff are already handling a server-side issue on your account.
One Bot fails and the others work#
Cursor staff traced several October cases to the model provider's safety filter refusing one Bot's history, often security or biology research content. A reset does not clear it. Start the work in another or a new Bot, and do not ask other Bots to read or continue the stuck chat, or they may hit the same block.
Match the message#
| Message | What to do |
|---|---|
| Bot failed to respond on every Bot | Check status; resend; otherwise follow the order above |
| Failed to send | Restart the app; check status before any Reset |
| Can't reach your computer | Retry, restart, then Recover |
| Your computer is asleep | Click the preview to wake it; do not Recover or Reset |
| Reset failed with a partial-state warning | Cursor's side during the October 8 incidents; do not retry |
Our full troubleshooting guide lists more messages and the release that fixed each one.
Frequently asked questions#
Why did all my Bots stop at once?#
Every Bot shares one cloud computer. If it is stuck, unreachable or updating, every Bot fails together. Check status first; if it is green, use the recovery order.
Why does only one Bot fail?#
Staff traced October cases to a safety filter refusing that Bot's conversation history. Every new message carries the history, so every reply is refused. Resetting the computer does not help; use another or a new Bot.
When should I Reset?#
Last. Reset restores the last saved snapshot and can lose recent unsynced work. Try Retry, restart, Recover and Update Bot's Computer first, and never Reset during an open incident.