Grok BotGuide

Update

Grok Bot update failed

Grok Bot update failed on one of two different buttons. Settings, Updates, Check for Updates, then Restart to Update, replaces the desktop app and does not reset the cloud computer.

Update under Grok Bot's Computer rebuilds that machine. On a slow update, Keep waiting is the safe default. Backup not ready means wait, not Reset.

What Update, Recover, and Reset each remove

Why the native method fails

The native method is to press Reset because the update sits still, or because the dialog says Backup not ready or Agent busy. Official computer recovery says the opposite. Backup not ready means the computer's data is not safely backed up yet. Grok Bot offers the update again after the backup finishes. Reset to force it can drop unsynced bots and files. Agent busy means a bot could not pause in time, so the computer was not updated. Let that bot finish, then update again.

Do not start a second Update or Reset while one is already running. Repeated resets can interrupt a restore that is still finishing. If Recover or Reset fails, use Retry Recovery or Retry Reset once, then stop and contact support.

Steps

  1. Decide which update you started. The app update is Check for Updates and Restart to Update. The computer update is Update under Grok Bot's Computer in the same Settings, Updates section. On iPhone and Android the computer controls are Update Computer and Reset Computer under Settings, Bot, Bot Computer.
  2. If the label still changes, or it says Update still running, leave it. An update can take several minutes while a large image downloads or data transfers. Reconnecting and Recover usually take a few minutes. Continue in Background is allowed. Choose Recover only if the update looks stuck and the app offers Recover computer. If recovery is not offered, keep waiting.
  3. Update and Recover keep synced bots, files, and logins. Both remove installed apps and packages on the computer. A turn that cannot pause is discarded. Reset is the only one that can also drop recent bots and files that have not synced. Chat history lives outside the computer, so an update is not how you protect chats, and it is not how you delete them either.
  4. After the computer comes back, apt packages, daemons, and other installed software are gone even when /workspace files survived. Keep a package list in a file and ask the Bot to reinstall. Idle machines also sleep, and background processes die. That is expected after an image rebuild, not a second failure of the update button.
  5. WhatsApp linked-device state is an exception staff called out. A computer refresh keeps /workspace, the browser profile, and ~/.config. It does not keep ~/.local/state, so a WhatsApp linked-device session can vanish. Plan to link that device again. Do not treat the missing session as proof the whole computer reset itself.
  6. Can't reach plus failed Recover and Reset, right after an update, is sometimes a lost app login rather than a dead machine. Staff said bots, files, and logins live on the remote computer, and Recover or Reset need a working session. Fully quit, sign out and sign in, or reinstall the app and sign in. Then retry the computer control once.

Limits

If the computer view is up and bots are only silent, do not update or reset to refill usage. If the phone on the same account still works and the desktop is black, do not Reset. If both devices fail, including cellular, wait before another computer button. Days of failure after Update, Recover, and Reset already ran are a staff restore, not a third click.

Cleaning up that never ends after a Reset often means the backend finished and the dialog missed the signal. Fully quit, reopen, and Recover if the computer is still down. Do not launch a second Reset to finish the first. Stopped at 50 percent Starting is a server-side bad state. Wait a few minutes. Bot data is usually still there.

FAQ

Does Restart to Update wipe my bots?

No. That control updates the desktop app. Updating the desktop app does not reset the cloud computer. The computer control is the separate Update under Grok Bot computer.

The dialog says Backup not ready. What do I click?

Nothing destructive. Wait until the update is offered again. Do not Reset to force a backup that has not finished.

It says Agent busy. Is the update broken?

A bot could not pause. Let it finish, then update again. Do not stack a second update on top.

My packages disappeared after a successful update. Is that a bug in the button?

Staff say Update keeps files and logins and rebuilds the OS image, so apt packages, apps, and daemons are removed. Keep a list in a file and reinstall.

Recover and Reset both failed after the update. What did staff try first?

A fresh login. Fully quit, sign out and back in, because those computer buttons need a working app session.

Related

Sources

  • Computer recovery
  • Official troubleshooting
  • Update then lost session
  • Packages wiped
  • WhatsApp session
  • Cleaning up