# Grok Bot not responding? Fix "Bot failed to respond" Bot failed to respond usually means a service incident, one failed reply or a stuck cloud computer. Check the status page, resend, then take the fixes in order. *From Learn Grok Bot, an independent guide (not affiliated with SpaceXAI or Cursor). Web version: https://learngrokbot.com/not-responding Last verified: 2026-10-06.* **Bot failed to respond** means the reply to your message failed, and the banner doesn't say why. Check the **Grok Bot** row on [status.cursor.com](https://status.cursor.com) first, because during an incident the only fix is to wait. With no incident open, send your message again. **In short** - An open incident on the status page means wait. Don't reset the computer or reinstall the app while it's open. - No incident: send the message again, then quit Grok Bot fully and reopen it. - When every Bot fails, even in a new chat, the cloud computer they share is stuck. Install any update that's waiting. **Reset** comes last. - A reset keeps your Bots, chats, files and logins. It removes installed apps and packages, and it can lose very recent changes. - Still failing after one reset: email hi@cursor.com with the request ID and your version. ## What the message looks like The message is a red banner above the message box. Its title is **Bot failed to respond**, and the line under it reads "Something went wrong while generating the reply. Try again." ![A dark red banner with a warning triangle. Its title is Bot failed to respond and the line under it reads Something went wrong while generating the reply. Try again. A round close button sits at its right end](https://learngrokbot.com/assets/shots/not-responding-banner.png) *This wording appears whether the cause is an incident or a stuck computer, so the banner alone can't tell you which you have.* Image: @IvankoListen on X (https://x.com/IvankoListen/status/2106974446481518679) A Bot can also go quiet with no banner: you send a message and no reply comes. The finder in the next section handles both. ## Find the fix for your case The same banner has several causes, and each has its own fix. Answer up to three questions about what you see, and the finder gives you the cause and the fixes to try, in order. **Interactive: Not responding: which case is yours?** Open it: https://learngrokbot.com/widgets/not-responding-finder.html What it does: Answer up to three questions about a Grok Bot that isn't responding (what's on screen, whether status.cursor.com shows an incident on the Grok Bot row, and whether one Bot or every Bot is affected) and get the likely cause with the fixes to try, in order. Its content as text: ### Not responding: which case is yours? Answer up to three questions. You get the likely cause and the fixes to try, in order. Start at question 1. Each answer links to the next question or to your fix. Question 1 #### What do you see? - A red banner: Bot failed to respond · Or Failed to send under your message · Go to question 2 → "Open [status.cursor.com](https://status.cursor.com) and find the Grok Bot row. Is an incident open?" - No reply and no message · The Bot has gone quiet · Go to question 2 → "Open [status.cursor.com](https://status.cursor.com) and find the Grok Bot row. Is an incident open?" - A message about my usage limit · Such as Weekly usage limit reached · Your fix: weekly usage has run out → "Your weekly usage has run out" - Reconnecting, or a notice that the app can't reach my computer · In the sidebar or over the chat · Your fix: the app can't reach the computer → "The app can't reach your Bots' computer" Question 2 #### Open [status.cursor.com](https://status.cursor.com) and find the Grok Bot row. Is an incident open? - Yes, an incident is open · The row doesn't read Operational, or an incident names Grok Bot · Your fix: wait for the incident to clear → "An incident is open: wait for it to clear" - No, the row reads Operational · No incident is open · Go to question 3 → "Send “hello” to a different Bot, or in a new chat. What happens?" Question 3 #### Send “hello” to a different Bot, or in a new chat. What happens? - It answers · Only one Bot or one chat is stuck · Your fix: one reply failed, or one quiet Bot under it → "One reply failed, and your computer is working" - It fails or stays quiet too · None of my Bots answer · Your fix: every Bot fails → "Every Bot fails: the computer they share is stuck" The six fixes Service incident #### An incident is open: wait for it to clear The fault is on Cursor's side, and nothing you do in the app makes it clear sooner. 1. Watch the status page until the incident is marked **Resolved**. 2. Quit Grok Bot fully and reopen it. 3. Send your message again. A message sent during an incident isn't retried for you. Don't **Reset** the computer and don't reinstall the app. Neither fixes an incident, and a reset now can lose very recent changes. Usage #### Your weekly usage has run out The week's included usage is used up. Your Bots start again when the week resets. 1. To wait, read the message: it says how long until the reset. 2. To keep going now, turn on on-demand usage or move to a bigger plan. [What to do when usage runs out](https://learngrokbot.com/usage-running-out) has both. Connection #### The app can't reach your Bots' computer Your Bots, files and logins are safe while the app reconnects. 1. Wait a few minutes, then choose **Retry**. 2. Still stuck? Follow the recovery order in [Can't reach your computer](https://learngrokbot.com/cant-reach-computer). Don't **Reset** while the app says **Reconnecting**. One request #### One reply failed, and your computer is working All your Bots share one cloud computer. Another Bot answered, so the computer is fine and the trouble is with this request or this chat. 1. Send the message again. 2. Quit Grok Bot fully and reopen it. 3. Start a new chat with the same Bot and send the request there: click **New chat**, type the Bot's name and click its row. 4. Same failure in the new chat? Send support the request ID. Don't **Reset** the computer. It's the part that works. One quiet Bot #### One quiet Bot: check whether it's waiting for you A Bot stops and waits when it needs an approval, an answer or a sign-in. A chat can also stop showing new messages while the Bot carries on. 1. Look for a card that's waiting for you, and answer it. 2. Click a different Bot in the sidebar, then click back. That reloads the chat. 3. Send “Stop now”, then ask again. 4. Quit Grok Bot fully and reopen it. Don't use **Update** or **Reset** here. They restart the computer's connection, which makes the wait longer. Shared computer #### Every Bot fails: the computer they share is stuck All your Bots work on one cloud computer. When it gets stuck, every Bot fails the same way, even a new one. 1. Quit Grok Bot fully and reopen it. 2. Check your weekly usage. 3. Install any update that's waiting. 4. Reset the computer one time. A reset removes the apps and packages installed on it. 5. Still failing? Write to support. Each fix in your list links to its steps in the next two sections. ## Work through the fixes in order The six fixes are in the order to try them, with the likeliest causes first. Stop as soon as your Bot answers. Only the last one removes anything, and its step says what. **Walkthrough: Fix a Bot that isn't responding** ### Step 1: Check the status page Open [status.cursor.com](https://status.cursor.com) in a browser and find the row named **Grok Bot**. The app doesn't show service status, so an incident appears only on that page. ![The status.cursor.com page in a phone browser. One row is named Grok Bot, with the word Operational in green at its right end and a strip of daily bars under it, most green and a few red or yellow](https://learngrokbot.com/assets/shots/not-responding-status-row.png) 1. Find the row named **Grok Bot**. Cursor's other products have rows of their own. 2. **Operational** means no incident is open. During an incident this word changes, and the page lists the incident with its updates. Image: Cursor forum (https://forum.cursor.com/t/t-f86577-cannot-connect-on-windows-macos-and-iphone-since-11-sep/171962/1) - **An incident is open.** Wait until the page marks it **Resolved**. Don't **Reset** the computer or reinstall the app while you wait: neither fixes an incident, and a reset can lose very recent changes. Then send your message again, because a message sent during an incident isn't retried. - **The row reads Operational.** Go on to the next fix. ### Step 2: Send the message again With no incident open, wait a moment and send the same message again. On a message marked **Failed to send**, click **Resend**. ![The left half of a Bot failed to respond banner whose second line reads This request has been rate limited, try again shortly.](https://learngrokbot.com/assets/shots/not-responding-rate-limited.png) *Read the second line before you resend. This one names its cause: the request was rate limited, so give it a little longer.* Image: Cursor forum (https://forum.cursor.com/t/grok-bot-dev-team-orchestration-feedback/172777/1) **Model provider is overloaded** takes the same fix: wait a moment, then send again. > **You should see** > > A status line such as **Working on it** shows while the Bot works, and then the reply arrives. ### Step 3: If the Bot is silent, see whether it's waiting for you When a Bot goes quiet with no banner, check whether it stopped to ask you something. Scroll to the end of its chat and look for a card: an approval, a question, a sign-in or a request for a secret. ![An approval card in a Bot's chat. It asks Allow Demo Meeting Prep to run a command?, carries an orange Needs approval tag, and has three buttons: Always allow, Allow once and Deny](https://learngrokbot.com/assets/shots/not-responding-waiting-card.png) 1. **Needs approval** is the tag on a card the Bot is waiting on. The Bot's row in the sidebar turns orange and starts **Waiting for you**. 2. Answer with **Allow once** or **Deny**, and the Bot carries on. No card? Click a different Bot in the sidebar, then click back, which reloads a chat that has stopped showing new messages. If the Bot is busy on the wrong thing, send “Stop now”, then ask again. ### Step 4: Quit Grok Bot fully and reopen it Quit the whole app, then open it again. Closing the window leaves the app running. Diagram: The Grok Bot app on your device and the cloud computer your Bots work on, joined by a connection. You quit and reopen the app. The cloud computer keeps working the whole time, and the app makes a fresh connection to it. - The app → The cloud computer: fresh connection - Note on The app: quit, then reopen - Note on The cloud computer: your Bots keep working - **Mac:** open the **Grok Bot** menu in the menu bar and choose **Quit Grok Bot**, or press Cmd+Q. - **Windows:** right-click the Grok Bot icon in the system tray and choose **Quit**. - **Phone:** swipe the app away, then open it. > **You should see** > > The app opens with your Bots in the sidebar. Send a short message to any Bot. A reply means you're done. ### Step 5: Check your weekly usage Click your picture at the bottom left of the app, then **Weekly usage**. ![The account menu with Weekly usage at 2 percent at the top, then Get Grok Bot for mobile, Support, Settings, Add account and Log out. A panel beside it shows Weekly usage, Resets in 1 day, 2 percent, then On-demand, Spend this cycle, 0 of 50 dollars, and Change limit](https://learngrokbot.com/assets/shots/not-responding-weekly-usage.png) 1. The percent is how much of this week's included usage is gone. 2. **Resets in** counts down to the next week's usage. 3. **On-demand** is paid usage past the weekly amount, shown as spent against your limit. At 100%, with on-demand off or spent, your Bots stop until the reset. [Usage running out](https://learngrokbot.com/usage-running-out) has what to do then. Below 100%, usage isn't the cause. ### Step 6: Install any update that's waiting Open **Settings** from the same menu and choose **Updates**. The page holds two updates: one for the app, and one for your Bots' computer. A computer update keeps your Bots, files and logins, and removes the apps and packages installed on the computer. ![The Updates page of Settings. Under Grok Bot Updates: Update Track, Automatic Updates, Version 0.68.1 and a Check for Updates button. Under Grok Bot's Computer: Update Grok Bot's Computer, with the line Your computer is on the latest version](https://learngrokbot.com/assets/shots/not-responding-updates.png) 1. **Check for Updates** looks for a newer app. If it finds one, choose **Restart to Update**. Versions before 0.63 could show **Bot failed to respond** when weekly usage ran out. 2. When a computer update is waiting, an **Update** button shows on this row. Click it, then click it again when it reads **Click Again to Confirm**. A computer update takes a few minutes. If a window says **Update still running**, choose **Keep waiting**. > **You should see** > > The row reads “Your computer is on the latest version”. Send your message again. ## Reset the computer only as a last step If every Bot still fails and no incident is open, the cloud computer your Bots share is stuck. **Reset** rebuilds it from your last saved data, which costs you the apps and packages installed on it and can cost very recent changes. The button is in the desktop app, at the bottom of **Settings** > **Updates**. ![The row Reset Grok Bot's Computer on the Updates page. Its text reads Start fresh if the computer gets stuck. It's rebuilt from your last saved snapshot, so very recent changes may be lost. A red Reset button sits at the right](https://learngrokbot.com/assets/shots/not-responding-reset.png) - **Kept:** your Bots, your chats, and the files and logins that were already saved. - **Removed:** apps and packages installed on the computer. You reinstall those afterwards. - **At risk:** very recent changes, when the computer can't be reached to save them first. Click **Reset** and confirm. The rebuild takes a few minutes, and the computer is ready as soon as the app reconnects. Reset once only: if the app says **Reset failed**, choose **Retry Reset** one time and then stop, because another reset can interrupt a restore that's still finishing. ## What only support can fix, and what to send Some stuck computers can only be rebuilt from Cursor's side. Email hi@cursor.com when one of these is true. - Every Bot still fails after one reset, and the status page shows no incident. - **Reset failed** shows again after **Retry Reset**. - One Bot fails on the same request in a new chat, while your other Bots answer. The request ID lets support find the exact failure. Here is an email with that and everything else support asks for. **An email to hi@cursor.com** - "Account email: you@example.com": the address you sign in with - "Version: 0.68.1 on a Mac": Settings, then Updates, shows it - "Bot: Meeting Prep": the Bot that failed - "On screen: Bot failed to respond (screenshot attached)": the exact words - "Request ID: paste it here": from Copy request ID - "When: today at 2:40 PM, Pacific time": with your time zone - "Already tried: resent, quit and reopened, updated, reset once": saves a round of questions To get the request ID, right-click the message that failed and choose **Copy request ID**. If the menu doesn't offer it, that message has no ID you can copy: send the error text and a screenshot instead. Leave passwords, codes and secret values out of the email. ## Messages that look similar A Bot also goes quiet behind these messages. Each one has its own page. | On screen | What it is, and where to go | |---|---| | "Weekly usage limit reached", or a warning that you're at 75% or 90% of your weekly usage limit | The week's included usage is gone or nearly gone. See [Usage running out](https://learngrokbot.com/usage-running-out). | | **Reconnecting**, "Can’t reach your computer" or **Couldn't Reach Grok Bot's Computer** | The app has lost its connection to the cloud computer. See [Can't reach your computer](https://learngrokbot.com/cant-reach-computer). | | An open incident on the status page | The service is having trouble for many people at once. See [Is Grok Bot down?](https://learngrokbot.com/is-grok-bot-down) | | **Authentication error**, or a sign-in screen that keeps coming back | A sign-in problem, with fixes of its own. See [Sign-in and linking](https://learngrokbot.com/sign-in-and-linking). | | The Bot says a website blocked it or showed a CAPTCHA | The site is turning away the cloud computer. See [Logins and CAPTCHAs](https://learngrokbot.com/logins-and-captchas). | | **Update required**, or any other message | Look it up in [Error messages](https://learngrokbot.com/error-messages). | With your Bots answering again, the next step is knowing the computer they share, so an update or a reset never costs you work. **Next:** [The shared computer](https://learngrokbot.com/shared-computer) One cloud computer sits behind all your Bots. See what lives on it, and what survives an update or a reset. ### Can I fix a Bot that isn't responding from my phone? You can do the first fixes on the phone: check the status page, send the message again, and close and reopen the app. Updating and resetting the computer are done in the desktop app. - 2026-10-06: First published. ## Sources - [Cursor Help Center: Grok Bot FAQs (Is Grok Bot down?)](https://cursor.com/help/grok-bot/faqs) - [Cursor Help Center: Grok Bot How Tos (troubleshooting, request ID, updates)](https://cursor.com/help/grok-bot/how-to) - [Cursor Help Center: Grok Bot computer (Update, Recover, Reset)](https://cursor.com/help/grok-bot/computer-recovery) - [Cursor Help Center: Get help](https://cursor.com/help/grok-bot/get-help) - [SpaceXAI docs: Troubleshooting](https://docs.x.ai/grok-bot/troubleshooting) - [SpaceXAI docs: Use the computer and apps](https://docs.x.ai/grok-bot/computer-and-apps) - [SpaceXAI: Grok Bot changelog (v0.58.0, v0.62.0, v0.63.0, v0.66.0)](https://x.ai/changelog/bot) - [Cursor status page](https://status.cursor.com/) - [Cursor forum: staff on a stuck computer and what a reset keeps](https://forum.cursor.com/t/grokbot-bot-failed-to-respond/168984) - [Cursor forum: staff on why every Bot fails at once](https://forum.cursor.com/t/grok-bot-failed-to-respond/170235) - [Cursor forum: staff on when not to reset](https://forum.cursor.com/t/fixing-the-bug-grok-bot-failed-to-respond/170954) - [Cursor forum: staff on resending after an incident](https://forum.cursor.com/t/grok-bots-failing-to-respond-again/173658) - [Cursor forum: staff on a chat that stopped showing new messages](https://forum.cursor.com/t/my-grok-bot-seems-to-be-stuck/173860) - [Cursor forum: staff on quitting from the Windows system tray](https://forum.cursor.com/t/grok-bot-windows-cant-reach-computer/170462) - [Image: the Bot failed to respond banner (@IvankoListen on X)](https://x.com/IvankoListen/status/2106974446481518679) - [Image: the rate-limited banner (Cursor forum)](https://forum.cursor.com/t/grok-bot-dev-team-orchestration-feedback/172777/1) - [Image: the Grok Bot row on the status page (Cursor forum)](https://forum.cursor.com/t/t-f86577-cannot-connect-on-windows-macos-and-iphone-since-11-sep/171962/1)