Grok Bot: Message failed to send in agent chat

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

In the Grok Bot desktop app’s agent chat, sending a message or replying under a thread sometimes shows the toast: “Message failed to send.”

Steps to Reproduce

  1. Open Grok Bot, open an agent chat.
  2. Send a normal message or reply under a thread.
  3. App shows toast: “Message failed to send.”

Expected Behavior

Message delivers.

Operating System

Other

Version Information

Not provided (Grok Bot desktop app)

Additional Information

Product: Grok Bot desktop app (agent chat)
Account: [email protected]
When: Friday Sep 18, 2026 ~8:25 PM America/Toronto
Agent: Ellis

Happened in a short burst of messages around 8:25 PM Toronto. No Request ID on the toast.

Also emailed [email protected] (message/thread id 1a0b710c8e234f30) and CC [email protected].

Does this stop you from using Cursor

No - Cursor works, but with this issue

Update: The failed sends happened when I was sending a burst of messages into the agent chat at once. Looks like chat/send reliability breaks under message storm load, not a single-message failure.

The issue is still persisting on my end (going on for 3 days now).
Rather than a permanent downtime, it behaves like a flapping connection: the app keeps alternating between a working state and complete disconnection roughly every 10 to 15 minutes.
Symptoms:

  • When it drops, clicking “Check for Updates” immediately returns:
    Couldn't check for updates. Check your connection and try again.
  • All outgoing prompts result in Failed to send.
  • After a few minutes, connectivity restores itself on its own, showing You're up to date, and messages go through again—before dropping again shortly after.

Environment details:

  • Client version: 0.57.1 (Stable track)
  • OS: macOS
  • Computer status: Your computer is on the latest version

Anyone else experiencing this exact 10–15 min drop pattern?

Hey, thanks for the report.

@TheAviv - what you hit that evening was a temporary issue on the service side that delivers messages to the Grok Bot. It’s been fixed. Messages sent during that short window didn’t go through, and only showed up as Failed to send when you reopened the app later. Anything sent after that is delivering normally, including your retries. No need to reset anything or reinstall. If you still see a message from that evening marked as failed, just hit Resend on it.

@StupidYas - what you’re describing looks different. Drops every 10 to 15 minutes with alternating connected and disconnected states, plus Couldn't check for updates. That looks more like a network issue than the same incident, so let’s look at it separately. To avoid mixing two different cases in one thread, please start a separate thread for your case and include:

  • Are you behind a corporate network, VPN, or proxy?
  • Does the drop pattern still happen if you switch to another network, like a mobile hotspot?
  • Rough time of the last drop, with your timezone.

With that, we can dig in further. Let me know if the issue comes back for either of you.

Thanks @deanrie — that pointed me in the right direction.

I don’t see the issue on Android with the same account. On desktop, after switching networks the problems went away (Failed to send / “Couldn’t check for updates” / sync banner).

So this was on my network side, not a Grok Bot outage. Appreciate the help.

Thanks @deanrie. Confirmed on our side: sends after that evening window are delivering normally again. No reset or reinstall needed. Will Resend any leftover failed messages from that short window if they still show as failed.

Same report is also on ticket T-F96779.

Glad to hear things are sorted out for both of you.

@TheAviv, yep, exactly. Everything after that short window on the evening of September 18 has been delivering normally. No reset or reinstall needed. If you still see a message from that window marked as failed, just hit Resend. You don’t need to track the email duplicate separately, it’s the same case.

@StupidYas, thanks for sharing the results. Since switching networks fixed it and Android with the same account didn’t have the issue, that really points to the network side, not Grok Bot. If the flapping comes back on the same connection, you can check whether there’s a VPN, proxy, or corporate filter between you and the service. If needed, start a separate thread with details.

If either of you starts seeing failures again, post here and we’ll take a look.