Error quick reference: find fixes by the exact error message
When you encounter a Grok Bot error, first match it by the exact error message. The official troubleshooting principle is just one: start with the least destructive step, and most problems can be solved with a single full restart.
Rest assured on one thing first: even if the desktop or mobile app disconnects, the Bot's cloud work continues and tasks will not be interrupted along with it.
The desktop app ships with 37 interface languages (including Simplified Chinese and Traditional Chinese), but the error messages included in the official troubleshooting documentation are all in English, so copying the original English text directly for comparison is the most accurate way to troubleshoot.
Symptoms: common error messages
- Sign-in and account (follow step 1): Sign-in does not complete, sign-in loop or persistent authentication errors, Legacy Privacy Mode, SSO or Grok Business seat sign-in failure.
- Runtime and cloud computer (follow step 2): Bot failed to respond, Model provider is overloaded, Setting up your Grok Bot…, Update still running, Taking longer than usual, An agent couldn't pause in time, Couldn't Reach Grok Bot's Computer, Reconnecting, Automation run rate limit exceeded, Voice chat failed.
- Integrations and settings (follow step 3): Local tools are turned off, Zoom error 4700, AADSTS50011.
Quick checks (spend two minutes first)
- Full restart: On Mac, choose Quit from the menu bar to fully quit Grok Bot—not just closing the window—then reopen and retry.
- Check service status: Open status.cursor.com and look at the Grok Bot row (troubleshooting.md:49-51). The app does not display service status; the status page is the officially designated place to check, and you can subscribe to updates.
- Wait first for newly appeared errors: Some authentication errors disappear on their own as the session refreshes if you wait 30 to 60 minutes.
Troubleshooting steps
Step 1: Sign-in and account errors, match one by one
Sign-in does not complete
Keep Grok Bot open and let the browser finish authentication. After confirming the browser shows that Cursor sign-in succeeded, if the app does not switch back automatically, return manually. If that still does not work, click Sign in again on the welcome screen; if you are already in the app, use Sign In with Cursor in the settings. Finally, confirm that your account actually has access to Grok Bot.
Sign-in loop or persistent authentication errors
- Update the desktop app to the latest version, sign out, and sign back in.
- Clear the browser cache and cookies for cursor.com and x.ai, and sign in again in an incognito window.
- On the desktop, sign in once more at x.ai/bot with the same Cursor account; if the loop happens on mobile, sign in on the desktop first.
- If the error appeared only recently, wait 30 to 60 minutes before retrying.
Legacy Privacy Mode error
Meaning: the account's current data mode does not allow the storage required by Grok Bot. Update the Cursor account data settings, or contact your organization administrator.
SSO or Grok Business seat sign-in failure
Organization SSO: complete the organization sign-in; do not switch to another personal account. Self-serve Grok Business seat: in the browser choose Sign in with Grok, using the Grok account that holds the seat.
Step 2: Runtime and cloud computer Grok Bot errors, match one by one
First determine whether it is a server-side issue, then match the error by its exact message.
Grok Bot down?
Open status.cursor.com and check the Grok Bot line to subscribe to status updates (troubleshooting.md:49-51). If the status page shows an incident: wait for the incident to be resolved, then send the message again. Do not Reset the computer or reinstall the app—neither can fix a service problem, and Reset may also lose your latest unsaved changes (:53-56).
"Bot failed to respond" / "Model provider is overloaded"
Cause: When the status page shows no incident, the official guidance is to treat it as a transient problem: wait a bit and resend once (troubleshooting.md:58-59).
Fix:
- Wait a while first, then send the message again exactly as before.
- If there is still no reply, fully quit the Grok Bot and reopen it.
- If the computer shows Reconnecting or Couldn't Reach Grok Bot's Computer, follow the recovery sequence below.
- If the computer is connected and the same prompt still fails: contact support with the error title, request ID, and a screenshot of the computer status (:58-65).
"Setting up your Grok Bot…" / "Update still running" / "Taking longer than usual"
Cause: First-time setup and computer updates naturally take a few minutes, and even longer when downloading a large image or transferring data (troubleshooting.md:69-75).
Fix:
- If the progress is still changing, keep waiting—Keep waiting is the safe choice.
- If the progress stops or fails, switch to the "computer unreachable" recovery sequence below.
- Only choose Recover computer if the update appears stuck and the app offers it; if this option is not available, keep waiting (:77-80).
Update says files are not backed up yet: Wait a while and try again; do not force it with Reset; if the message keeps appearing, contact support (:82-85).
"An agent couldn't pause in time, so the computer was not updated"
Cause: A Bot is currently working, so the update could not be inserted (troubleshooting.md:86-88).
Fix: Let that Bot finish its current work, then go to Settings and select Update again.
"Couldn't Reach Grok Bot's Computer" / "Reconnecting"
Cause: The cloud computer is temporarily unreachable. Bot profiles and chat history are stored outside the computer, so they will not be lost because of this (troubleshooting.md:90-94).
Fix (official recovery sequence, starting with the least destructive, :96-109):
- Wait first, then select Retry; do not Reset during this time (:98-100).
- Fully quit the Grok Bot and reopen it (:101).
- When an update prompt appears, open Settings → Computer and select Update Bot's Computer (:102-103).
- If it still cannot connect, or the update is stuck and Recover computer appears, select it—in the confirmation dialog it is called Recover Grok Bot's Computer (:104-106).
- Only use Reset after trying all of the above. On mobile, select Settings → Bot → Bot Computer and choose Reset Computer; updating and recovering the computer must be done on desktop (:107-109).
Note three things (:111-116):
- Reconnecting and Recover usually take only a few minutes; you can select Continue in Background and do something else in the meantime.
- Do not start a second Update or Reset while one is still running; repeated Resets may interrupt a recovery that has not yet completed.
- If Recover or Reset fails: use Retry Recovery / Retry Reset once, then stop and contact support.
Project directories like node_modules and Python venvs are not saved and must be reinstalled after an update, recovery, or reset (:129-130).
"Automation run rate limit exceeded"
Cause: All routines combined are limited to at most 300 per hour and at most 200 for a single one; exceeding the limit causes failure (cursor/help-grok-bot-routines.md:77).
Fix:
- If a particular routine frequently hits the limit, have the Bot narrow its trigger conditions or widen its scheduling interval.
- Failed runs are not retried automatically: rerun them with Test on desktop, or send the request again if triggered by a webhook (cursor/help-grok-bot-routines.md:79).
Note: You may see this error even if you do not run much yourself—all Grok Bot routines share a single limit; this is a known issue on the official side and a fix is in progress (cursor/help-grok-bot-routines.md:78).
"Voice chat failed"
Cause: The call dropped and automatic reconnection failed; the notification may say Connection lost, No connection, or The call ended unexpectedly (cursor/help-grok-bot-voice-chat.md:54).
Fix: Select Dismiss, check your network, then select Start voice chat to redial (cursor/help-grok-bot-voice-chat.md:55-57). If it says the microphone was denied, go to system settings and allow Grok Bot to use the microphone; if it says no microphone was found, connect one and try again (:58).
Step 3: Integration and setup errors, match each one
"Local tools are turned off. The user has set local tool access to Never."
Cause: The cloud computer and the local computer have two separate sets of permissions. First check the policy of Settings → Computer → Your computer → Execution on this computer—before the desktop list appeared, this was called Execution on Local Computer (troubleshooting.md:359-362).
Known issue: If the setting is already Always allow or Ask every time and this error still appears, it is a known issue on the Cursor side. Your setting is not wrong—restarting, reinstalling Grok Bot, or changing the setting will not eliminate the error (:367-371).
"Zoom error 4700" (authorization failed, Invalid redirect)
Cause: Starting Zoom authorization from the Grok Bot desktop app always fails at present; this is a known issue on the official side (cursor/help-grok-bot-connect-apps.md:127-128).
Solution: No workaround for now—nothing you change on your end will help, so wait for an official fix; the official documentation will be updated once Zoom can connect (cursor/help-grok-bot-connect-apps.md:129; docs/grok-bot/computer-and-apps.md:243-245).
"AADSTS50011" (SharePoint connection reports redirect URI mismatch)
Cause: When a Cursor team admin connects SharePoint by selecting Integrations → Application-level permissions from the dashboard page, Microsoft throws this error before the consent prompt. The Microsoft app named in the error belongs to Grok, not your organization, so changing anything in the Entra admin center is useless (cursor/help-grok-bot-connect-apps.md:130-131).
Solution: Connect using Delegated permissions instead (cursor/help-grok-bot-connect-apps.md:132-137; docs/grok-bot/computer-and-apps.md:249-256):
- Cursor dashboard → Integrations → SharePoint card, select Connect team (or Reconnect if setup was already started), and choose Delegated permissions.
- Enter the Microsoft tenant ID (e.g.
contoso.onmicrosoft.com, or the GUID under Microsoft Entra ID > Overview). - Sign in with Microsoft; for most work or school tenants, a Microsoft administrator needs to consent to Sites.Read.All once.
- Each team member signs in with their own Microsoft account the first time the Bot uses SharePoint, and can only see sites their account could already open.
If a member sees "This team does not have the SharePoint integration": it means the administrator has not yet completed the Delegated sign-in above, and the integration stays unavailable until that is done (cursor/help-grok-bot-connect-apps.md:138).
Step 4: Nothing matches—gather materials and prepare to escalate
Collect the exact error text, when it occurred, and the checks you have already done; if you can copy a request ID, right-click the message and choose Copy request ID—if that item is not in the menu, the message has no request ID, so attach the error text and screenshots instead (troubleshooting.md:462-465). Check against the official troubleshooting documentation (docs.x.ai/grok-bot/troubleshooting) item by item; if there is still no solution, move on to the escalation criteria.
Escalation criteria
Can reinstalling the app fix it?
Usually not. The official documentation explicitly states that reinstalling generally does not resolve login issues, so don't waste time on it.
Which issues require contacting support directly?
Some session and account linking failures (including login loops), as well as access blocks caused by failed phone verification, cannot be fixed on your end according to the official documentation. Email support@x.ai (troubleshooting.md:456) and include: the complete error text, the steps you have already tried, and whether the problem started with a SuperGrok or X Premium+ link; for a phone verification block, also attach a screenshot of the block.