"Bot failed to respond" errors after a computer Reset
Staff say the Oct 8 errors are fixed. If one Bot still fails while the others reply, see the safety filter issue.
Update, Oct 9: Fixed. At 6:20 AM ET, staff said the capacity issue "has been resolved since about 21:00 UTC on Oct 8" (5 PM ET), and said a fix for a separate regional failure went out Thursday evening, UTC. We changed this entry from a known issue to a fix.
Update, Oct 8: At 1:43 PM ET, staff described a separate cause that started about 9:30 AM ET. Some Bots couldn't reach their model because of a capacity limit on Cursor's side. Staff said a reset won't change anything for it.
- Status: Fixed. Staff said at 6:20 AM ET on Oct 9 that the capacity problem cleared at about 5 PM ET on Oct 8, and that Bots "should be replying normally again." A separate failure that hit "some users in your region," reported from Hong Kong, got a fix Thursday evening, UTC, and two users confirmed it on Oct 9.
- First seen: Oct 6, in a forum report posted at 6:17 PM ET. Staff called that round fixed at 7:26 PM ET, and the errors came back overnight into Oct 8.
- Symptoms: Every Bot replies "Bot failed to respond," even in a new chat. For some users, a Reset then fails with "Reset failed" and leaves the computer in a partial state.
- What to do now: Quit and reopen Grok Bot, then send the message again. If only one Bot still fails while your others reply, it may be a safety filter block instead.
Some users see every Bot return "Bot failed to respond," then try Reset and get "Reset failed" with the computer in a partial state. Forum staff gave several status notes on Oct 8.
At 5:55 AM ET, Colin, a Cursor community support engineer, said the server-side issue that stopped Bots from replying "was resolved earlier today," and that a separate short problem behind "Reset failed" had cleared. At 2:57 PM ET, staff member kevinn told a user on 0.68.1 that the same errors "aren't caused by anything on your end" and are still being tracked. "Your bots and their data are safe," he wrote.
Why it matters#
Resetting feels like the fix, but it can make things worse. The help center says Reset can lose "very recent changes" if the computer can't be reached to save them.
How to use it#
If your Bots still fail after the fix:
- Fully quit Grok Bot and reopen it. On Mac, choose Quit from the menu bar.
- Send the message again.
- If every Bot still fails, check status.cursor.com for a Grok Bot incident before you touch Reset.
- If only one Bot fails while the others reply, it may be the safety filter issue. Staff said a Reset won't help with that either.
Good to know#
- If it keeps failing, staff ask for the time of your last attempt in the forum thread. Another staff member also asked for the conversation ID: right-click the Bot in the sidebar, then choose Copy conversation ID.
- The help center's general rule is one Retry Reset at most, then contact support. For these errors, staff say not to retry at all.
