# Grok Bot error messages: what each one means Look up a Grok Bot message by its exact words: Bot failed to respond, Backup not ready, Update required, Needs auth, Expired and more, each with what to do. *From Learn Grok Bot, an independent guide (not affiliated with SpaceXAI or Cursor). Web version: https://learngrokbot.com/error-messages Last verified: 2026-10-06.* Every Grok Bot message here is quoted exactly as it appears on screen, with what it means and what to do about it. Type a few words of yours into the box below, or pick the place it showed up. **In short** - The exact words of a message say which part of Grok Bot is talking: a reply, the usage meter, the cloud computer, a sign-in, a plugin, an approval or the app itself. That decides the fix. - Each entry has a tag: **Wait**, **Fix it**, **Ask someone**, **No fix needed** or **Not Grok Bot**. - Many messages only need you to wait. No fix on this page starts with a reset. - When nothing works, support needs the exact words, a screenshot and the request ID. ## Look up your message The decoder holds 72 messages, each with its other wordings. Type two or three words from yours, or choose where it appeared. **Interactive: Grok Bot error messages: look up yours** Open it: https://learngrokbot.com/widgets/error-messages-decoder.html What it does: Type part of a Grok Bot message, or pick where it appeared, and each of 72 entries opens to the exact words on screen, what they mean and what to do. With scripts off it is a plain list in seven groups. Its content as text: ### What does your message say? Type a few words of it, or pick where it appeared. Each message opens to what it means and what to do. Every message is listed below, grouped by where it appears. Tap one to open it. #### In a chat Banners above the message box, notes under a message, and cards a Bot posts. **“Bot failed to respond” · Fix it · A red banner above the message box** Image: [@tprayaga on X](https://x.com/tprayaga/status/2096792378778775725) **On screen**: “Bot failed to respond” then “Something went wrong while generating the reply. Try again.” **What it means**: The reply to your last message failed. The banner reads the same for a service incident, one bad request and a stuck cloud computer. **What to do**: Check the **Grok Bot** row on [status.cursor.com](https://status.cursor.com). With no incident open, send the message again. [Bot not responding](https://learngrokbot.com/not-responding) has the rest of the fixes, in order. **Also appears as** - “This request has been rate limited, try again shortly.” as the second line: wait a minute, then send again. - “Something went wrong. Technical details: EAGAIN” as the second line: send again. If it comes back, give support the code along with the request ID. **“Model provider is overloaded” · Wait · In a chat, when a reply fails** **What it means**: The service that runs the model behind your Bot is too busy to take the request. **What to do**: Wait a moment and send the message again. If it keeps coming back, [send support the request ID](https://learngrokbot.com/not-responding#support). **“Failed to send” · Fix it · Under a message you sent, with Resend and Delete** **What it means**: Your message didn't reach the Bot. **What to do**: Click **Resend**. If every message fails, [check for an incident](https://learngrokbot.com/is-grok-bot-down), then see [Can't reach your computer](https://learngrokbot.com/cant-reach-computer). **Also appears as** - “Message not delivered” then “Something went wrong talking to your computer. Please try again.”: an earlier wording, on the phone. The message is marked “Not delivered”. Tap **Retry**. **“SEND AFTER RECONNECT” · Wait · A divider above your message, in the phone app** **What it means**: The app has lost its connection and is holding your message. **What to do**: Leave it. The message goes when the connection returns. If it never does, check your phone's connection, then see [Can't reach your computer](https://learngrokbot.com/cant-reach-computer). **“Rate limit exceeded.” · Wait · A banner in a chat** **On screen**: “Rate limit exceeded.” then “You've reached the rate limit. Please wait a bit before trying again.” **What it means**: Requests reached the service faster than it allows. **What to do**: Wait a few minutes, then send your message once. **“Model name is not valid: "grok-4-7-0907"” · Wait · In a chat, when a reply fails** **What it means**: Grok Bot's servers asked for a model under a name that didn't exist. On 2026-09-07 this showed for about 20 minutes on Mac, iPhone and Android, and nothing done in the app made a difference. **What to do**: Wait, then send the message again. If it returns, send support the request ID and the time you sent the message. **“This turn was stopped after 50 minutes so it would not hang. Send a message to pick up where it left off.” · Fix it · A grey note in the chat** **What it means**: Grok Bot ended a reply that had been running for 50 minutes. **What to do**: Send a message, such as “carry on”, and the Bot picks up where it left off. For a long job, [ask for it in smaller pieces](https://learngrokbot.com/usage-running-out#big-jobs). **Also appears as** - “A background task was stopped after 50 minutes so it would not hang.”: the same stop, for work running in the background. **“A background task was stopped after 3 tool calls in a row timed out; the computer may be unresponsive.” · Fix it · A grey note in the chat** **What it means**: Three commands in a row got no answer from the cloud computer, so Grok Bot stopped the task. **What to do**: Send the Bot a short message as a test. If that fails too, the computer is stuck: take [the fixes in order](https://learngrokbot.com/not-responding#fixes). **“Something went wrong on our end. Please try again.” · Fix it · A notice headed Error, at the top of the phone app** **On screen**: “Error” then “Something went wrong on our end. Please try again.” **What it means**: The app hit a failure it has no specific message for. **What to do**: Try again, then close the app fully and reopen it. If the same step fails again, send support a screenshot and what you were doing. **Also appears as** - “Grok Bot hit an unexpected error” with **Try Again**: the same thing, filling the screen on an iPhone. - “Something went wrong” with **Try Again**: in the list of Bots on Android. **“Could not create the Bot. Please try again.” · Fix it · When you create a Bot** **What it means**: The new Bot wasn't saved. **What to do**: Try again. If it fails twice, [quit the app fully and reopen it](https://learngrokbot.com/not-responding#quit), and [check for an incident](https://learngrokbot.com/is-grok-bot-down). **Also appears as** - “Couldn't replace the main Bot”: the same failure when you change your Main Bot. **“Voice chat failed” · Fix it · When a voice chat drops** **What it means**: The call lost its connection and ended. **What to do**: Choose **Dismiss**, check your internet connection, then choose **Start voice chat** again. **Also appears as** - “The call ended unexpectedly.” or “The realtime connection failed.”: the line under the title. **“The secret was not saved. Try again.” · Fix it · On a secret card** **What it means**: The value you typed didn't save. **What to do**: Enter it again on the card and choose **Save securely**. Don't paste the value into the chat instead. **Also appears as** - “Could not fill into the page”: the card couldn't type the secret into the website, often because the page had moved on. Fill in a new card if the Bot asks again. **“[REDACTED]” · No fix needed · In what a Team Bot shows of its work** **What it means**: The Bot used one of its saved secrets, and the value is hidden wherever it would have appeared. **What to do**: You don't need to do anything. Hiding the value keeps the secret out of the chat. **“Team Bots Not Available” · Ask someone · When you open a link to a Team Bot** **What it means**: Your account can't use Team Bots. They are for members of a Cursor team that has them turned on. **What to do**: Ask your Cursor team's admin. **Also appears as** - “Bot Not Found”: the Bot was removed, or it isn't shared with you. Ask its owner. **“This conversation can't run on your computer because your privacy mode is stricter than the bot owner's.” · No fix needed · In a chat with a teammate's Team Bot** **What it means**: Your Cursor privacy setting is stricter than the owner's, so in this chat the Team Bot can't work on your cloud computer. It can't use your files there or the sites you're signed in to. **What to do**: Nothing is broken. Attach any file the Bot needs to the chat. #### Usage Banners above the message box, the Usage & Billing page of Settings, and the Spending page on cursor.com. **“Weekly usage limit reached. It resets in 6 days.” · Wait · A banner above the message box, with Increase limits and an upgrade button. The number of days changes** Image: [@filedfyi on X](https://x.com/filedfyi/status/2107109569512014270) **What it means**: This week's included usage is used up. With on-demand usage off, your Bots stop until the reset. **What to do**: Wait for the reset, or [turn on on-demand usage with a cap](https://learngrokbot.com/usage-limits#on-demand). To make next week last, see [Usage running out](https://learngrokbot.com/usage-running-out). **Also appears as** - “You’ve hit your weekly usage limit. It resets in 1 day.”: an earlier wording of the same banner. - “You've reached your Grok Bot usage limit” then “Your included Grok Bot usage limit has been reached. It resets in 3 days. Enable on-demand spend to continue.”: an older wording. Its last sentence can also read “Increase your on-demand limit to continue.” or “Upgrade to get more usage.” **“You’re at 75% of your weekly usage limit. It resets in 3 days.” · No fix needed · A banner above the message box, with Get More Usage** **What it means**: This is a warning, and nothing has stopped yet. **What to do**: Find what's using up the week with [the leak finder](https://learngrokbot.com/usage-running-out#leak). **Also appears as** - “You’re at 90% of your weekly usage limit. It resets in 2 days.”: the second warning. - “You've used over 75% of your weekly usage limit. Resets in 6 days.” with **Get more usage**: the phone app's wording. **“No included usage available on your plan right now” · Fix it · In Settings, on the Usage & Billing page** **What it means**: The Cursor account you're signed in to has no plan, link or trial that includes Grok Bot. **What to do**: Already paying? [Find out why the app doesn't see your plan](https://learngrokbot.com/sign-in-and-linking#finder). If not, [pick a route in](https://learngrokbot.com/pricing#route). On an app older than version 0.63, update first: those versions could show this on a paid plan once the week ran out. **Also appears as** - “Your trial has ended. Upgrade to continue using Grok Bot.”: shown with it once a trial is used up. - “Start a Grok Bot trial to send messages” then “This account can try Grok Bot now.” with **Start Trial**: the account hasn't claimed its trial yet. - “Your plan has no included Grok Bot usage” and “You are out of usage”: wordings from August 2026. **“Your team has reached its usage limit” · Ask someone · A banner in the desktop app, on a team plan. The date changes** **On screen**: “Your team has reached its usage limit” then “Cloud agents launched from Grok Bot draw on your team's Cursor usage, which is separate from your Grok Bot message allowance.” then “Please reach out to an admin to enable on-demand usage, or return on 9/14/2026 when your limit resets.” **What it means**: Cloud Agents that your Bots started have used up your team's Cursor usage. That's a different meter from Grok Bot's weekly usage. **What to do**: Ask your admin to turn on on-demand usage, or wait for the date in the message. [Which meter is this?](https://learngrokbot.com/usage-limits#meter) **Also appears as** - “Your Cloud Agent runs are blocked until your usage resets on October 11 (in 13 days).”: the same limit, in an email from Cursor. **“Grok Bot pauses at the limit until it resets. Set an on-demand limit to keep going.” · No fix needed · On the Grok Bot card on cursor.com, under Spending** **What it means**: On-demand usage is off. At 100% your Bots stop until the weekly reset. **What to do**: Leave it as it is, or [set an on-demand limit](https://learngrokbot.com/usage-limits#on-demand). **Also appears as** - “Weekly usage used up. Grok Bot now uses on-demand spend, up to your limit, until it resets.”: the week is gone and on-demand is on, so Bot work is now billed, up to your monthly limit. - “On-demand spending is currently disabled”: the same page, when on-demand is off. **“This Bot's owner has reached their usage limit” · Wait · In a chat with a Team Bot** **What it means**: The account paying for this chat is out of usage. In your own chat with a teammate's Team Bot, that account is yours. **What to do**: Check [your own weekly usage](https://learngrokbot.com/usage-limits#see). **“You hit your weekly limit. Switch to SuperGrok Plus for more usage.” · Not Grok Bot · In the Grok app, under the heading Weekly limit reached** **On screen**: “Weekly limit reached” then “You hit your weekly limit. Switch to SuperGrok Plus for more usage.” **What it means**: The Grok chat app has a weekly limit of its own. It says nothing about Grok Bot, whose usage is counted on your Cursor account. **What to do**: There's nothing to do in Grok Bot. Your Grok Bot usage is in the Grok Bot app, in **Settings** > **Usage & Billing**. [How the two meters differ](https://learngrokbot.com/usage-limits#separate). **Also appears as** - “Weekly Limit reached” then “You will now use Extra Usage Credits. Switch to SuperGrok Plus for higher limits.”: the Grok app again. - “Weekly SuperGrok Limit”: the Grok app again. - “Other Models usage limit reached” then “Switched to grok-4.6 after reaching Other Models usage limit.”: a banner in the Cursor editor, about Cursor's own usage. #### The computer Sidebar notices, dialogs and the Updates page of Settings. All of them are about the cloud computer your Bots share. **“Can’t reach your computer” · Wait · A notice at the top of the sidebar, with Retry and Recover computer** Image: [@testerlabor on X](https://x.com/testerlabor/status/2098343229317931086) **On screen**: “Can’t reach your computer” then “Your Bots are safe — they just can’t be loaded right now. If it doesn’t come back on its own, recover it — your files and logins are kept, but installed apps and packages are removed.” **What it means**: The app has lost its connection to the cloud computer your Bots work on. Your Bots, files and logins are safe. **What to do**: Wait a few minutes and click **Retry**. Leave **Recover computer** alone until you've been through [the steps that come before it](https://learngrokbot.com/cant-reach-computer). **Also appears as** - “Couldn't Reach Grok Bot's Computer” then “Your Bots, files, and logins are safe. If it doesn't reconnect on its own, recover Grok Bot's computer to keep the data.”: the same message as a dialog, pictured here. - “Can't reach your computer — your messages are safe.”: the phone app's wording. **“Reconnecting” · Wait · A pill at the top of a chat** **What it means**: The app is trying to get the computer back by itself. Until it does, a chat shows its saved messages. **What to do**: Give it a few minutes, and don't reset the computer while it tries. Still there? [Start at the first step](https://learngrokbot.com/cant-reach-computer#retry). **Also appears as** - “Reconnecting to your computer…” with “Retrying…”: the sidebar's wording. - “Showing saved messages” then “This conversation may be out of date and will refresh when the connection returns”: the note under the pill. - “Grok Bot is having trouble connecting” with **Retry**: the same state on the start screen. **“A firewall, VPN, or proxy such as Zscaler may be blocking the connection” · Fix it · On the start screen, under the heading Can't Reach Grok Bot's Computer** **On screen**: “Can't Reach Grok Bot's Computer” then “A firewall, VPN, or proxy such as Zscaler may be blocking the connection” then “*.cursorvm.com” then “Ask IT to allow this domain, then try again” **What it means**: Something on your network is blocking the app. The computer itself is fine. **What to do**: Pause any VPN or proxy and click **Retry**. On a work network, [send IT the addresses to allow](https://learngrokbot.com/cant-reach-computer#network). Don't recover or reset, because the computer is fine. **“Can't reach New Bot's screen” · Fix it · On the Computer tab of a Bot's details, with Retry. Your Bot's name takes the place of New Bot** **What it means**: The app can't show that Bot's live screen. **What to do**: Click **Retry**. If the sidebar also says it can't reach your computer, [start there](https://learngrokbot.com/cant-reach-computer). **“Grok Bot couldn’t finish setting up” · Fix it · On the start screen, during first-time setup** **On screen**: “Grok Bot couldn’t finish setting up” then “gateway-unreachable: gateway createAgent unreachable (network)” **What it means**: Setup couldn't reach Grok Bot's servers to create your computer. **What to do**: Quit the app fully and reopen it, then try a second network such as a phone's hotspot: [how to test your network](https://learngrokbot.com/cant-reach-computer#network). **Also appears as** - “Something went wrong” then “gateway-unreachable: gateway recordVoiceCall unreachable (dns)”: the same kind of failure, when a voice chat starts. - “Retry exhausted for onboarding-bot-provision after 3 attempts”: setup tried three times to create your first Bot and stopped. If reopening the app doesn't clear it, send this line to support. **“Starting your computer” · Wait · When the app opens, or after an update** **What it means**: The cloud computer is being started or rebuilt. First-time setup can take several minutes. **What to do**: Keep the app open. If the line hasn't changed for a long while, see [setup that never finishes](https://learngrokbot.com/cant-reach-computer#find). **Also appears as** - “Updating your computer”: the same wait, during an update. - “Booting up the computer” and “Starting desktop”: lines seen while the computer's screen loads. **“Update still running” · Wait · In the window Updating Grok Bot's Computer** **On screen**: “Update still running” then “A large image download or data transfer can take a few minutes. Keep waiting while the update finishes.” **What it means**: The computer update is still working through a large download or a data transfer. **What to do**: Choose **Keep waiting**. Don't start a second update or a reset. See [when a step stalls](https://learngrokbot.com/cant-reach-computer#stalls). **“Update unavailable” · Wait · When you start a computer update** **On screen**: “Update unavailable” then “Your computer's files aren't ready. Try again in a moment.” **What it means**: The update can't start yet. **What to do**: Try again in a few minutes. **“Backup not ready” · Wait · On the Updates page of Settings, when a computer update won't start** **What it means**: The computer's data isn't safely backed up yet, so the update is held back. **What to do**: Wait for the app to offer the update again, which it does once a backup has finished. Don't reset to force it. If the message never clears, [write to support](https://learngrokbot.com/cant-reach-computer#support). **Also appears as** - “Agent busy”: a Bot couldn't pause in time, so the update didn't run. Let that Bot finish, then update again. **“Update failed” · Fix it · In the update window** **On screen**: “Update failed” then “The update couldn't finish. Agent Computer is still on its previous image.” then “Your files and logins are kept; installed apps and packages are not” then “Any agent turn that cannot pause is discarded.” **What it means**: The update didn't finish, and the computer is still on its old version. **What to do**: If the app offers **Recover computer**, that is the next step. [What a recovery costs](https://learngrokbot.com/cant-reach-computer#recover). **“Reset failed” · Fix it · After a reset, with Dismiss and Retry Reset** **On screen**: “Reset failed” then “The reset couldn't finish. Grok Bot's computer may be in a partial state — retry to run the reset again.” **What it means**: The reset didn't finish, and the computer may be left partly rebuilt. **What to do**: Click **Retry Reset** once. If it fails again, stop and [write to support](https://learngrokbot.com/cant-reach-computer#support). **“Recover failed” · Fix it · After a recovery** **On screen**: “Recover failed” then “The recovery couldn't finish, so Grok Bot's computer may still be unreachable. Your Bots, files, and logins are safe.” **What it means**: The recovery didn't finish. Your Bots, files and logins are safe. **What to do**: Click **Retry Recovery** once. If it fails again, stop and [write to support](https://learngrokbot.com/cant-reach-computer#support). **Also appears as** - “The computer recovery failed. Try again.”: an older wording, in a red bar at the foot of Settings. **“Taking longer than expected” · Wait · In the window Recovering Grok Bot's Computer** **On screen**: “Taking longer than expected” then “The recovery is still running — recreating Grok Bot’s computer can take a few minutes. You can keep waiting, or continue in the background.” **What it means**: The recovery is still running. **What to do**: Choose **Keep waiting**, or let it carry on in the background. **“Computer is low on disk space” · Fix it · A banner at the top of a chat, with Go to Disk Saver** **On screen**: “Computer is low on disk space” then “Disk Saver is auditing usage and will propose safe cleanup. Nothing is deleted without confirmation.” **What it means**: The disk of your Bots' cloud computer is nearly full. It isn't about your laptop, and your chats aren't affected. **What to do**: Choose **Go to Disk Saver**. Disk Saver is a Bot that lists what's using the space and asks before it deletes anything. **Also appears as** - “Computer is critically low on disk space”: the same warning, with less room left. **“TLS certificate untrusted: SELF_SIGNED_CERT_IN_CHAIN” · Fix it · A row in the Network Debugger, in Settings on Windows** **What it means**: Something between the app and Grok Bot is opening the encrypted connection and signing it again, such as a company gateway or antivirus software. **What to do**: In the security software, trust Grok Bot and turn off scanning of encrypted connections for it. On a work network, ask IT. [The steps and the addresses](https://learngrokbot.com/cant-reach-computer#network). **Also appears as** - “Computer endpoint unavailable” and “ConnectError”: other rows of the same check, when the computer can't be reached at all. **“Couldn't check for a newer version.” · Fix it · On the Bot Computer sheet in the phone app** **What it means**: The phone app couldn't find out whether your Bots' computer has an update waiting. **What to do**: Check from the desktop app instead, in **Settings** > **Updates**. [Updating the computer](https://learngrokbot.com/cant-reach-computer#update). **“Search unavailable” · Wait · When you search a Bot's files** **What it means**: File search runs on the cloud computer, and it can't run right now. **What to do**: Try again in a minute. If other things are failing too, see [Can't reach your computer](https://learngrokbot.com/cant-reach-computer). #### Sign-in and linking The sign-in page in your browser, the link page for SuperGrok and X Premium+, and the plan screen. **“Authentication error” · Fix it · A red banner above the message box, on an app that's still signed in** Image: [@LubaYudasina on X](https://x.com/LubaYudasina/status/2099316980951982241) **On screen**: “Authentication error” then “If you are logged in, try logging out and back in.” **What it means**: It looks like a sign-in problem and usually isn't one: the app still shows your account and your Bots. Logging out and back in doesn't clear it. **What to do**: Open **Settings** > **Updates** and install the update for Grok Bot's computer, if one is offered. [The steps, and what to try next](https://learngrokbot.com/sign-in-and-linking#auth-error). **“There was an issue authenticating” · Fix it · On the browser page Sign in to Grok Bot with Cursor** **What it means**: The sign-in didn't finish. **What to do**: Take [the five sign-in steps](https://learngrokbot.com/sign-in-and-linking#sign-in) in order, starting with an app update. **Also appears as** - “Something went wrong” then “An unexpected error occurred. Please try again.”: the same, on cursor.com. - “Something went wrong. Please try again.”: the same, on accounts.x.ai, while signing in with a Grok account. **“Access blocked, please contact support.” · Ask someone · A red line on Cursor's sign-in page** **What it means**: Cursor has blocked sign-in for this account, and nothing on your side lifts it. **What to do**: Email hi@cursor.com with the account's email address and a screenshot. [What to put in the email](https://learngrokbot.com/sign-in-and-linking#support). **Also appears as** - “Account Blocked” then “Your account has been blocked due to suspicious usage.”: a full page on cursor.com. Its last words can also be “due to suspected violation of our policies.” Only support can review it. **“Your Cursor account is already linked to a different Grok account.” · Fix it · A red line on the link page** **What it means**: This Cursor account already has its one link, and a link can't be undone or moved. **What to do**: Use the Grok or X account it's linked to, or link from a different Cursor account. [The link rules](https://learngrokbot.com/sign-in-and-linking#link). **“That Grok account is already linked to another Cursor account.” · Fix it · A red line on the link page, with Email the linked account, Go back and Switch accounts** **What it means**: This Grok account already has its one link, to a different Cursor account. **What to do**: Choose **Switch accounts** and sign in to the Cursor account that holds the link. [The link rules](https://learngrokbot.com/sign-in-and-linking#link). **“Grok Bot access requires an active SuperGrok, SuperGrok Plus, SuperGrok Heavy, or X Premium+ subscription. Upgrade this Grok account, then link it again.” · Fix it · On the link page** **What it means**: The Grok or X account you linked has no plan that includes Grok Bot. **What to do**: Upgrade that account, then link it again. Linking a second time is right in this case. [Fix a link that won't take](https://learngrokbot.com/sign-in-and-linking#link). **Also appears as** - “Your Grok account is linked, but SuperGrok Lite doesn't include Grok Bot. Access requires SuperGrok, SuperGrok Plus, SuperGrok Heavy, or X Premium+ — after upgrading, link your Grok account again.”: the same, on the plan screen, for SuperGrok Lite. **“You need a Pro plan to use Grok Bot.” · Fix it · On the plan screen, when the app opens** **On screen**: “You need a Pro plan to use Grok Bot.” then “Upgrade to continue.” **What it means**: The Cursor account you're signed in to has no plan or link that includes Grok Bot. **What to do**: Already paying for one? [Start from what you pay for](https://learngrokbot.com/sign-in-and-linking#finder). Otherwise, [pick a route in](https://learngrokbot.com/pricing#route). **Also appears as** - “Grok Bot needs a Pro+ plan” then “Upgrade to Pro+ to send messages with Grok Bot.”: the wording before 2026-08-26, when Cursor Pro didn't yet include Grok Bot. **“Verify your Grok account again” · Fix it · While linking, with Re-link Grok account. The plan named in it changes** **On screen**: “Verify your Grok account again” then “Your Grok sign-in expired before we could verify your SuperGrok Heavy subscription. Link your Grok account again to finish claiming.” **What it means**: The link stopped partway: your Grok sign-in timed out before the subscription was checked. **What to do**: Choose **Re-link Grok account** and go through the link in one sitting. [Fix a link that won't take](https://learngrokbot.com/sign-in-and-linking#link). **“User is not assigned to this application” · Ask someone · On your company's single sign-on page** **What it means**: Your company's sign-on system hasn't given you the Cursor app, which Grok Bot signs in through. **What to do**: Ask IT to assign you to the company's existing Cursor app. Grok Bot doesn't need an app of its own there. #### Plugins Plugin pages in Connect Apps, sign-in cards in a chat, and the other service's own pages. **“Needs auth” · Fix it · On a plugin's page in Connect Apps, beside an account, with Authenticate** **What it means**: The plugin is installed, but its sign-in was never finished or has lapsed. **What to do**: Click **Authenticate** and sign in on the app's own page. [If that doesn't clear it](https://learngrokbot.com/plugins#needs-auth). **Also appears as** - “Added”: installed. It doesn't mean signed in. - “Disconnected”: the sign-in has dropped. The fix is the same. **“Waiting for Gmail authorization...” · Fix it · On a card in a chat, with Reopen. The app's name changes** **What it means**: Grok Bot is waiting for you to finish a sign-in in your browser. **What to do**: Click **Reopen** to bring the sign-in page back, and finish within about 10 minutes. [More on reconnecting a plugin](https://learngrokbot.com/plugins#needs-auth). **“Cloudflare didn't finish connecting” · Fix it · On a plugin's page or its card, with Retry. The plugin's name changes** **What it means**: The sign-in for that plugin started and didn't complete. **What to do**: Click **Retry** and finish the sign-in in your browser. **Also appears as** - “X Money didn't finish connecting”: the same message, for another plugin. **“Couldn't start sign-in for Github. Details: Streamable HTTP error: Error POSTing to endpoint: bad request: Authorization header is badly formatted” · Ask someone · A red line on a plugin's page. The plugin's name and the details change** **What it means**: The plugin's sign-in couldn't begin. The words after Details are the other service's reason. **What to do**: Try once more later. If it repeats, nothing on your side fixes it: send support the plugin's name, your account email and the whole line. **Also appears as** - “Couldn't start sign-in for Ahrefs. Details: HTTP 429:” followed by a long technical line: the service is turning sign-in attempts away for now. Try again later. - “Couldn't start sign-in: This plugin's OAuth client is not configured. Set Client ID and Client Secret in the plugin settings.”: the plugin itself is set up wrong. Report it to support with the plugin's name. **“Failed to load connector” · Fix it · On a plugin's page, with a red Error** **What it means**: Grok Bot couldn't start that plugin's connection. **What to do**: Uninstall the plugin, add it again and sign in. A server you added yourself has to be at a public https address: see [custom servers](https://learngrokbot.com/plugins#custom-mcp). **Also appears as** - “Failed to load connector. Details: spawn ${env:HOME}${env:USERPROFILE}/.paper/bin/paper ENOENT”: the plugin tried to start a program on a local computer. A Bot works in the cloud, so that plugin can't run there. **“Last sync failed. Sync now to try again.” · Fix it · On the 1Password plugin's page** **What it means**: The 1Password plugin couldn't refresh from your vault the last time it tried. **What to do**: Choose **Sync now**. **“Complete GitHub auth to sync installed plugins” · Fix it · In Manage plugins and skills, with Fix with Bot. The number changes** **On screen**: “Complete GitHub auth to sync installed plugins” then “5 installed plugins can't be fetched until Grok Bot's computer can read their source repository.” **What it means**: Some of your plugins come from a GitHub repository, and your Bots' computer isn't signed in to GitHub. **What to do**: Choose **Fix with Bot** and finish the GitHub sign-in it asks for. **“Disabled by team admin” · Ask someone · On a plugin, when you use Grok Bot through a Cursor team** **What it means**: Your Cursor team's admin has turned that plugin off for the team. **What to do**: Ask the admin to turn it on. **“Awaiting admin approval” · Ask someone · When you connect a Team Bot to Slack** **What it means**: Your Slack workspace needs an admin to approve new apps. **What to do**: Choose **Send request in Slack**, then **Check approval** once an admin has approved it. **“Access blocked” · Not Grok Bot · On Google's sign-in page, when you connect a Google plugin** **What it means**: Google refused the sign-in. On a company account, your Google admin hasn't approved the app named Grok. **What to do**: Ask your Google admin to trust the app named **Grok**: [the steps to send them](https://learngrokbot.com/gmail#fixes). Another browser won't clear it. **Also appears as** - “Your admin needs to review Grok”: the same block, before anyone has asked. Request access on that page if it offers a button. - “This app is blocked” then “This app tried to access sensitive info in your Google Account. To keep your account safe, Google blocked this access.”: another of Google's block pages. On a company account the same steps apply. **“OAuth callback failed.” · Fix it · In a browser tab, at the end of a plugin sign-in** **On screen**: “OAuth callback failed.” then “Close this tab and try connecting again.” **What it means**: The sign-in page couldn't hand its result back to Grok Bot. **What to do**: Close the tab, go back to the plugin's page and click **Authenticate** again. **“App configuration error” · Wait · On Vercel's page, when you connect the Vercel plugin** **On screen**: “App configuration error” then “The app redirect URL is invalid, please contact the app developer for support.” **What it means**: A fault in the Vercel plugin's sign-in. On 2026-09-21 it was a known issue, and retrying or reinstalling the plugin didn't get past it. **What to do**: There's nothing to change on your side. **“error 4700 (Invalid redirect)” · Wait · On Zoom's page, when you connect the Zoom plugin from the desktop app** **What it means**: A known fault, as of 2026-10-06: Zoom rejects the sign-in that the desktop app starts. **What to do**: There's no workaround, and no change on your side fixes it. It needs a fix from Cursor. #### Approvals and routines Approval cards, locked settings, and a routine's page. **“Expired” · Fix it · A tag on an approval card** **What it means**: The Bot asked for your approval during work you weren't watching, such as a routine, and nobody answered within about 10 minutes. The action didn't run. **What to do**: Ask the Bot to try the task again, and answer the new card. [Stop it happening on the next run](https://learngrokbot.com/approvals#expired). **Also appears as** - “Approval expired”: the card's heading. - “Always allow this in the future”: a button an expired card may offer. It saves a rule for that action. - “You can manage Auto-review in Settings”: the line at the foot of the card. **“Needs approval” · Fix it · A tag on a card in the chat** **What it means**: The Bot has stopped and is waiting for your answer. Nothing runs until you choose. **What to do**: Read the request, then choose **Allow once**, **Always allow** or **Deny**. [How to answer a card](https://learngrokbot.com/approvals#card). **Also appears as** - “Waiting for you”: the start of the Bot's row in the sidebar while a card is open. - “Bot needs your approval” with **Deny** and **Approve once**: the same request on the phone. - “Auto-review Paused This Action”: the heading on cards in older versions. **“Required by your admin” · Ask someone · On the Auto-review switch or a rule, in Settings** **What it means**: Your team's admin has locked that setting, so you can't change it. **What to do**: Ask your admin if it's getting in the way of your work. **Also appears as** - “Required by your admin. You can't edit or delete this rule.”: on a rule. - “Required by your admin. You can't turn this off.”: on a Team Bot an admin added. - “Disabled by your admin. You can't turn this on.” or “Your team's admin has turned off local egress.”: on **Route traffic through this computer**. **“Allow Grok Bot and all Bots to run commands on your local computer?” · No fix needed · The first time a Bot wants to use your own Mac or PC** **What it means**: A Bot wants to open a file or run something on the computer in front of you. That's separate from its cloud computer. **What to do**: Choose **Allow once** if you asked for that, or **Deny once** if you didn't. [The setting behind the question](https://learngrokbot.com/approvals#own-computer). **“Paused” · Fix it · On a routine's row, under Details** **What it means**: The routine is switched off and won't run. **What to do**: Turn its switch back on. [Other reasons a routine didn't run](https://learngrokbot.com/routines#fixes). **“You've been away for a bit — keep my routines running?” · No fix needed · A card from a Bot, with three choices: Keep them running, Pause them all, and Keep running, don't ask again** **What it means**: You haven't opened Grok Bot for a while, and the Bot is asking whether its routines should carry on. **What to do**: Pick one. [If a routine has stopped](https://learngrokbot.com/routines#fixes). **“This Bot keeps its routines on the server. Ask it in chat to change, pause, or delete one.” · Fix it · On a routine's panel, in versions from September 2026** **What it means**: In that version the routine panel could only be read. **What to do**: Update the app. Current versions have **Pause** and **Edit** on [the routine's page](https://learngrokbot.com/routines#pause). Asking the Bot in chat works in both. **“Deleting failed. Check your connection and try again.” · Fix it · In the window that confirms deleting a routine** **What it means**: The delete didn't reach Grok Bot. **What to do**: Check your connection and click **Delete** again. If it keeps failing, pause the routine so it stops running, and ask the Bot in chat to delete it. #### Updates and the app Messages about the app itself, on a computer and on a phone. **“Update required” · Fix it · A screen in place of the app, saying your version is no longer supported** **What it means**: Your app is too old to connect. A version stops working once it's well out of date and a newer one is out. **What to do**: Choose **Update**, then **Restart to update**. If the update fails, choose **Try again** or **Download the latest version**. On a phone, tap **Update Grok Bot**. Your Bots and chats belong to your account, so they're still there afterwards. **“New update available” · No fix needed · In the account menu, at the bottom left of the app** **What it means**: A newer version of the app is ready. Your Bots keep working in the cloud while the app restarts. **What to do**: Choose **Install**, then **Restart to update**. **“Notifications are off” · Fix it · In the phone app's Settings** **What it means**: Your phone isn't letting Grok Bot send alerts, so approvals and finished work won't reach you there. **What to do**: Choose **Open Settings** and allow notifications for Grok Bot. A fix that takes more than one step has a page of its own, and the entry links straight to the step. ## Read both lines of a message Most Grok Bot messages have two lines, and the second one is easy to skip. The title names what failed, and several different problems share it. The line under it holds the cause, when the app knows it. ![A dark red banner with a warning triangle. Its title is Bot failed to respond. The line under it reads Something went wrong. Technical details: EAGAIN](https://learngrokbot.com/assets/shots/error-messages-second-line.png) 1. The title. **Bot failed to respond** is on every reply that fails, whatever the reason. 2. The second line. Here it ends in a code, “EAGAIN”, which the usual wording doesn't have. Image: @dobroslav_dev on X (https://x.com/dobroslav_dev/status/2091932123326263505) - Search the decoder by the second line when the title brings up too much. - Copy the second line word for word when you write to support. They ask for the exact error text. ## When no fix works: what to send support Some messages have no fix on your side, and some fixes don't take. Then one complete email to hi@cursor.com saves a round of questions. **Put these in the email** - [ ] The exact words of the message, both lines, and a screenshot of it - [ ] The request ID: right-click the message that failed and choose **Copy request ID** - [ ] The email address on your Cursor account - [ ] Your Grok Bot version, and whether you're on a Mac, Windows, Linux, an iPhone or Android - [ ] The name of the Bot, and the fixes you've already tried The version is in **Settings** > **Updates**. [Bot not responding](https://learngrokbot.com/not-responding#support) lays the email out line by line, and covers a message that has no request ID. Leave passwords, sign-in codes and secret values out of it. ## Check: whose message is it? One habit saves more time than any single fix: asking who a message belongs to. A message from the Grok app, or from another company's sign-in page, can't be fixed inside Grok Bot. **Sort it: Sort each message by where it comes from.** Answer: - “Bot failed to respond” → Grok Bot (A banner in the Grok Bot app, above the message box.) - “Weekly usage limit reached. It resets in 6 days.” → Grok Bot (Grok Bot's own meter, counted on your Cursor account.) - “Weekly SuperGrok Limit” → The Grok app (The Grok chat app's limit. Your Bots carry on.) - “You hit your weekly limit. Switch to SuperGrok Plus for more usage.” → The Grok app (The Grok app again. Its weekly limit is a separate meter.) - “Your admin needs to review Grok” → Another company's page (Google's page. Your Google admin decides, and nothing in Grok Bot changes that.) - “error 4700 (Invalid redirect)” → Another company's page (Zoom's page, when the Zoom plugin tries to sign in.) A message that shows on every Bot at once often isn't yours to fix at all. The next page shows how to tell. **Next:** [Is Grok Bot down?](https://learngrokbot.com/is-grok-bot-down) One row on one status page says whether Grok Bot has an incident. See where it is, and what to do while one is open. ### The installer says Grok Bot isn't supported on my Mac. What now? The main download button gives you the build for Apple silicon. On a Mac with an Intel chip, get the Intel build from the list at [cursor.com/download/bot](https://cursor.com/download/bot). ### Why am I not getting notifications on my phone? Open **Settings** in the phone app. If it says **Notifications are off**, choose **Open Settings** and allow notifications for Grok Bot. On a computer, alerts don't show while Grok Bot is the window you're using. The Bot's row in the sidebar shows that it needs you. - 2026-10-06: First published. ## Sources - [Cursor Help Center: Grok Bot FAQs (service status, usage limit, disk space, approvals)](https://cursor.com/help/grok-bot/faqs) - [Cursor Help Center: Grok Bot How Tos (symptom table, request ID, Update required, reconnecting a plugin)](https://cursor.com/help/grok-bot/how-to) - [Cursor Help Center: Grok Bot computer (Backup not ready, Agent busy, Retry Recovery, Retry Reset)](https://cursor.com/help/grok-bot/computer-recovery) - [Cursor Help Center: Connect plugins (Google admin blocks, Disabled by team admin, Zoom error 4700)](https://cursor.com/help/grok-bot/connect-plugins) - [Cursor Help Center: Sign in to Grok Bot](https://cursor.com/help/grok-bot/sign-in) - [Cursor Help Center: Link SuperGrok for Grok Bot](https://cursor.com/help/grok-bot/supergrok) - [Cursor Help Center: Plans and billing](https://cursor.com/help/grok-bot/plans) - [Cursor Help Center: Voice chat with a Bot](https://cursor.com/help/grok-bot/voice-chat) - [Cursor Help Center: Store secrets securely](https://cursor.com/help/grok-bot/secrets) - [Cursor Help Center: Team Bots](https://cursor.com/help/grok-bot/team-bots) - [Cursor Help Center: Grok Bot on mobile (notifications)](https://cursor.com/help/grok-bot/mobile) - [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: Settings and notifications (settings an admin has locked)](https://docs.x.ai/grok-bot/settings-and-notifications) - [SpaceXAI docs: Approvals, security and privacy](https://docs.x.ai/grok-bot/approvals-security-and-privacy) - [SpaceXAI docs: Identity and access (single sign-on)](https://docs.x.ai/grok-bot/identity-and-access) - [SpaceXAI docs: Team Bots (secrets, Slack approval)](https://docs.x.ai/grok-bot/team-bots) - [Cursor docs: Grok Bot settings](https://cursor.com/docs/grok-bot/settings) - [SpaceXAI: Grok Bot changelog (Failed to send, the limit banner, v0.63.0)](https://x.ai/changelog/bot) - [Cursor: Grok Bot downloads](https://cursor.com/download/bot) - [Cursor forum: staff on the Model name is not valid error](https://forum.cursor.com/t/model-name-is-not-valid-grok-4-7-0907-grok-bot/170932) - [Cursor forum: staff on the Vercel plugin's App configuration error](https://forum.cursor.com/t/grok-bot-vercel-plugin-649-oauth-fails-with-app-configuration-error-redirect-url-is-invalid/168499) - [Cursor forum: staff on a plugin sign-in that is rate limited](https://forum.cursor.com/t/grokbot-ahref-connector-rate-limited/173206) - [Image: the Bot failed to respond banner (@tprayaga on X)](https://x.com/tprayaga/status/2096792378778775725) - [Image: the Weekly usage limit reached banner (@filedfyi on X)](https://x.com/filedfyi/status/2107109569512014270) - [Image: the Couldn't Reach Grok Bot's Computer dialog (@testerlabor on X)](https://x.com/testerlabor/status/2098343229317931086) - [Image: the Authentication error banner (@LubaYudasina on X)](https://x.com/LubaYudasina/status/2099316980951982241) - [Image: a Bot failed to respond banner with a code on its second line (@dobroslav_dev on X)](https://x.com/dobroslav_dev/status/2091932123326263505)