Grok Bot fails to respond to messages. The issue occurs across multiple conversations and also affects newly created bots, so it does not appear to be limited to one conversation.
Conversation ID from one affected conversation:
298cb650-dade-4f69-b1d2-8d6ef64e19f1
Already tried without success:
Closed and reopened Grok Bot
Used Reset Grok Bot’s Computer
Waited more than four hours
Tried other conversations
Created a new bot
The reset was an attempted fix, not the cause of the problem.
This appears similar to this report, which required the cloud computer hosting the bots to be recovered on Cursor’s side. Could you please check and, if necessary, reset or reprovision the Grok Bot computer associated with my account?
Steps to Reproduce
Open Grok Bot.
Open any existing conversation or create a new bot.
Send a message.
The bot fails to respond.
Hey, thanks for the detailed report. The conversation ID really helped, and you’re right, it’s the same class as in the thread you linked.
The cloud computer running your bots got stuck early this morning. Since all conversations and new bots run on the same machine, everything fails the same way with Bot failed to respond. The reset in settings didn’t work, and it’s not your fault. The machine is unresponsive in a way that also blocks the reset from shutting down safely. So nothing you tried on your side would’ve helped.
Also, since I subscribed less than 48 hours ago and haven’t had much opportunity to use the service, would it be possible to receive a credit for the downtime?
Hey, thanks for coming back with an update. It’s the same situation I described: the cloud machine running all your bots got stuck, and the self-serve Reset isn’t working. The machine isn’t responding, which blocks the reset from completing safely. The fact that the bots responded for a minute or two and then went quiet again fits this exactly.
This isn’t related to your setup and it’s not something you can fix on your side. I can’t give an exact ETA, but I’ll post here as soon as I have an update.
On credit for the downtime: account and billing requests are handled by our team at [email protected]. They’ll be able to look into your specific situation.
@tmast, you have a separate machine, so we’re looking at your case separately from this. I’ll update you when I have more info.
Hey @Diogo_Brito, @Abc3, you’re running into the same issue described earlier in this thread.
The cloud computer running your bots is stuck on our side. Since all conversations and new bots run on the same machine, they all fail the same way with “Bot failed to respond”. The self-serve Reset in settings doesn’t work here because the machine isn’t responding, and that also blocks a safe shutdown during the reset. So there’s nothing you can do on your side, and it’s not related to your setup.
@Abc3, thanks for the ticket number and conversation ID, that makes it easier to find your machine.
@Diogo_Brito, please send the conversation ID from any affected conversation, that’ll help us find your computer faster.
@atristannewman / @Diogo_Brito I couldn’t find any Grok Bot boxes associated to the e-mail you used to sign up for the forum. I’ll reach out to you via DM.
hey @Colin thanks for the quick fix - all my bots came back to life simultaneously a few minutes ago. A new “Disk Saver” bot was pushed (I assume by your team) which may have been the underlying issue.
For what it’s worth if its helpful - while my bots were down, I could still access the Computer view on all of them. UI was working fine, but that box seemed to be disconnected from the web.
