Grok Bot error message

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Error button flashes on screen and does not appear to do anything other than let me know that Bot can’t respond. No explanation, no error code, absolutely useless.

Steps to Reproduce

Anything, try and do anything in Grok Bot and the error pops up. Message “hello?” Open desktop (which strangely does load) , and type anything into Google search bar and nothing.

Expected Behavior

To be able to use this premium service that I paid for.

Screenshots / Screen Recordings

Operating System

iOS

Version Information

Grok Bot 1.2.0 (4226)

For AI issues: which model did you use?

No idea, because Grok Bot doesn’t tell me what it’s using. Part of the fun.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @MattTondreau, thanks for the report, and fair point about the error not telling you anything useful.

From what you’ve described, your Bot’s computer has gotten into a stuck state, which is why the desktop view loads but nothing actually responds.

The quickest fix is to reset it from the desktop app: open a Bot, go to Grok Both’s Settings > Updates, and hit Reset Grok Bot’s Computer. Your Bots, files, and logins are all kept (installed apps and packages get removed), and it takes a few minutes to finish. If it’s still unresponsive after the reset, let us know here and we’ll dig deeper on our end!

Thank you, that Reset did fix the problem!

Reset + Update 都做过了,仍然 Bot failed to respond。

Tickets: T-F1787 / T-F4465

Conversation ID: 7358fbc3-7b51-4d65-a5a5-b0e1d1128d63

Sam closed email: no backend reset from that channel.

Weekly usage 0%, Win/Mac/iOS, desktop opens.

Need engineering to recreate the agent computer.

Hey @Jimeng, following up on this one.

We checked on the account you reported and their Grok Bot computer recovered on August 23. It has been running normally since then, with messages going through again. The support ticket you referenced was also confirmed resolved and closed on August 24.

If they see “Bot failed to respond” again, please let us know here with a fresh Conversation ID and we will take another look.

Going to close this thread to make sure it doesn’t become home for many different user reports.