Most Grok Bot errors fall into four groups: usage ran out, the Bot’s cloud computer can’t be reached, an app lost its sign-in, or a rule (yours, your team’s or a safety check) stopped the action. Find your message below. Each one has what it means and what to do, taken from xAI’s and Cursor’s official help pages.
First, rule out an outage. Check the Grok Bot row on status.cursor.com, and status.x.ai for Grok itself. More in Is Grok Bot down?
“Grok was unable to finish replying”
Where you see it: users report this message in the Grok chat app and on grok.com, the regular Grok assistant. It isn’t one of the Grok Bot messages in xAI’s Grok Bot docs.
What it means: we couldn’t find an official xAI explanation. The safest reading is that the reply failed partway through.
What to do:
- Choose Retry, or send the message again.
- Check status.x.ai for grok.com, the apps or the models. In recent months it has listed incidents such as a grok.com outage (October 7, 2026) and wider model outages.
- Reload the page or restart the app, and check your connection.
If you see a failed reply inside Grok Bot, use the fixes in the next sections instead.
Usage limit notice (“reached your Grok Bot usage limit”)
What it means: your weekly included usage is used up. Cursor’s help says that if on-demand usage is off, Grok Bot stops until weekly usage resets.
What to do: open Settings → Usage & Billing. You can wait for the weekly reset, turn on on-demand usage or top-ups (depending on your plan), or upgrade. Tagged @bot requests also stop when usage runs out. See Grok Bot pricing.
Plan doesn’t include Grok Bot, or there’s an unpaid invoice
What it means: your account has no Grok Bot access. Plus, Free and SuperGrok Lite don’t include it. Since September 26, 2026, the app says why instead of showing a generic error.
What to do: check your plan, or pay the open invoice. On a Grok Business seat, the message tells you to ask your admin to connect your team.
“Starting your computer” / “Updating your computer” won’t finish
What it means: first setup or an update to the Bot’s computer is still running. xAI says that can take several minutes.
What to do: if progress is still changing, wait. If it stops or fails: retry, restart Grok Bot, check for an app update, then try Settings → Computer → Update Bot’s Computer.
The computer can’t be reached
What it means: the app can’t connect to your Bots’ cloud computer. Your Bots and saved conversations aren’t necessarily lost.
What to do, in this order: Retry → restart the app → Recover computer (keeps files and logins) → Update Bot’s Computer → wait for the replacement. Use Reset only if you accept losing recent unsynced work. If a firewall or VPN is blocking it, Grok Bot says it can’t reach the computer and offers Retry.
Legacy Privacy Mode error at sign-in
What it means: Grok Bot needs cloud data storage, and your Cursor account uses a data mode that doesn’t allow it.
What to do: change the data setting in your Cursor account privacy settings, or ask your organization admin.
“Blocked by a safety check”
What it means: a safety check blocked the Bot’s reply. The chat says Try a different message.
What to do: reword the request. If a chat’s very first message was blocked, resetting the chat now works.
“Disabled by team admin”
What it means: your Cursor team admin hasn’t allowed that app.
What to do: ask your admin to enable it. This is a different control from a Google Workspace admin block.
“Your admin needs to review Grok” / “Access blocked” (Google)
What it means: a company Google account hasn’t approved Grok as a third-party app. Grok Bot signs in to Google as “Grok”, not Cursor.
What to do: request access on the Google page, or have your IT admin mark Grok as Trusted in the Google Admin console (Security → Access and data control → API controls → App access control). Personal Gmail accounts don’t need this.
App shows “Needs auth” or “Disconnected”
What it means: “Added” only means installed, not signed in.
What to do: open the app in Connect apps and choose Authenticate (Authorize on the phone). If you revoked access in the service itself, remove the plugin and reconnect it.
Zoom error 4700 / SharePoint AADSTS50011
- Zoom 4700 (Invalid redirect): a known issue. Cursor says nothing on your end fixes it, and there’s no workaround yet.
- SharePoint AADSTS50011: a known issue with Application-level permissions. The workaround is to connect with Delegated permissions.
“Permission denied”, or local computer work refused
There isn’t one official “permission denied” message, but these are the usual causes:
- Local computer work refused: your Mac or PC has its own policy. Check Settings → Computer → Your computer → Execution on this computer. xAI recommends keeping it off unless a task really needs your local files.
- An action keeps asking for approval: look for an Ask first rule under Settings → General → Bot → Custom Rules, including rules your admin requires. Ask first beats Allow automatically.
- GitHub can’t see a repo: the Bot now stops and links you to the GitHub page where you grant access.
“Couldn’t upload an attachment” or a file can’t be read
What to do: on current versions, files can be up to 250 MB and videos up to 1 GB, with up to 20 attachments per message (200 MB total). Make sure the file isn’t password-protected, and try exporting it as PDF, CSV, text or an image.
“Failed to send”
What it means: your message didn’t reach the Bot. What to do: choose Resend, or Delete it.
@bot replies “Sign up for Grok Bot” or “Grok Bot isn’t set up yet”
- “Sign up for Grok Bot”: no Grok account is connected to that X account. Connect it on grok.com under Settings → Account.
- “Grok Bot isn’t set up yet”: your accounts are linked but you don’t have a Bot of your own yet. Create one, then tag again.
Related bots from the library
- Bot Doctor: catches stale routines, overlapping skills and risky permissions before they cause errors.
- Backup & Handoff: keeps important work outside the Bot’s computer, so a Reset doesn’t hurt.
- Usage Limit Maximizer: helps you stay under your weekly limit.
- Script This Routine: finds routines that could run as a small script instead.
Browse all Grok Bot templates.
Get the free setup guide
Most errors are easier to avoid than to fix. Our free 18-page setup guide covers safe setup, approvals and routines. Get the free guide
FAQ
Is “Grok was unable to finish replying” a Grok Bot error?
Not according to xAI’s Grok Bot docs. Users report it in the Grok chat app. Retry, then check status.x.ai.
What should I include when I contact support?
xAI asks for your Grok Bot version, operating system, the exact error, the Bot or routine name, the time and time zone, any request or conversation ID, and what you already tried. Never include passwords or codes.
Will Reset delete my chats?
No. Conversations are stored outside the computer. A Reset can lose recent unsynced files, though, so try Recover and Update first.
Why did my routine fail without an error?
The usual causes are a signed-out connector, a disabled routine, a deleted owner Bot or used-up usage. Since October 22, 2026, a signed-out connector shows a Reconnect card in chat, at most once a day.
Swarm School is an independent site. We’re not affiliated with xAI or Cursor.
Sources
- https://docs.x.ai/grok-bot/troubleshooting
- https://docs.x.ai/grok-bot/tag-on-x
- https://cursor.com/help/grok-bot/plans
- https://cursor.com/help/grok-bot/connect-apps
- https://x.ai/changelog/bot (v0.70.2 Oct 11, v0.71.2 Oct 14, Sep 26 and Sep 28 entries)
- https://status.x.ai
- https://status.cursor.com
- https://www.reddit.com/r/grok/comments/1qgykly/grok_was_unable_to_finish_replying_anyway_to_fix/ (user report of the message text only; not used for causes)
Swarm School is independent and not affiliated with Grok Bot’s makers. Features change; check the official docs for current details.