Grok Bot troubleshooting: sign-in, routines and a stuck computer
Start with the least destructive check. A Grok Bot's cloud work can continue while the desktop or iPhone app is disconnected, so restarting, deleting, or repeating work immediately can lose evidence or create a duplicate action.
The current official troubleshooting guide covers sign-in, setup, a stuck Bot, computer reconnects, routine failures, CAPTCHA handoffs, and usage limits. The steps below organise those checks by symptom.
Sign-in does not complete
- Keep Grok Bot open while Cursor authentication runs in the browser.
- Confirm the browser reports a successful sign-in.
- Return to the app manually if it does not regain focus.
- Try the sign-in control again and confirm the account currently has access.
Do not repeatedly create new sessions until you know whether the original authentication completed.
The computer says reconnecting or the Bot looks stuck
First check the conversation for new output and ask the Bot for its current step. If the cloud task is still progressing, leave it alone. If no progress appears, record the last visible action, error, URL, and whether a write may already have happened.
Use a fresh small task to separate a broken website or login from a broken Bot. Follow the official least-destructive order: tell the Bot “Stop now,” inspect and update if available, reconnect or restart only after the current state is understood, and use Reset Agent Computer only as a last resort because recent unsynchronised work can be lost.
A scheduled routine did not run
- Confirm the routine is enabled and belongs to the expected Bot.
- Check its schedule and time zone.
- Confirm the source account, file, or connector is still reachable.
- Inspect recent run history for an error, approval wait, or usage pause.
- Check whether a long absence caused unattended routines to pause.
- Run one safe test with current input after fixing the cause.
- If the problem remains for 24 hours with current software and a reproducible case, send the recorded evidence through the official support path.
A community missed-routine thread shows why this symptom matters, but it does not prove that every missed run has the same cause.
A login, two-factor check, or CAPTCHA appears
Take over the computer and complete passwords, passkeys, two-factor codes, CAPTCHAs, payment confirmations, identity checks, and other human-only steps yourself. The official security guide says not to put passwords or one-time codes in ordinary chat.
Do not teach bypasses, simulate human movement, or keep retrying until a website blocks the account. A dedicated connector is preferable when one exists; browser access still depends on the site's rules.
The Bot's browser is not your existing local Chrome session. Read Grok Bot cloud and local access before troubleshooting tabs, files or device-specific apps.
Usage is exhausted or unexpectedly high
Inspect the account's current usage page, stop broad or repeatedly failing work, and wait for the displayed reset or enable on-demand use only if that is the intended account choice. Record the task, retries, and result before drawing a conclusion.
Read Grok Bot plans and pricing for eligibility and separate weekly usage, then Where Grok Bot usage goes for a measurement ledger rather than relying on unverified community percentages.
Keep the evidence. Before retrying, capture the exact symptom, last completed action, current source state, approval state, and whether the intended result already exists.
The recipe
Get the bots this setup runs on.