Recover a computer
Member·6 minutes to read
What this does for you
This page orders every way to fix a stuck or broken computer from least to most destructive, and states exactly what each one keeps and what it throws away.
Before you start
- You are signed in as a member of the organisation the bot belongs to.
- You know which is wrong: the app around the computer (a stuck tab, a stale build) or the computer itself (a bot's screen will not open, or a task keeps failing).
- For the last three steps below, you can reach Settings → Updates.
Steps
Try these in order. Each one undoes less of your work than the next, so do not reach for Reset first.
| Step | Keeps | Loses | Disk |
|---|---|---|---|
| Retry | everything | nothing | unaffected |
| Restart the app | everything | nothing | unaffected |
| Check for an update | everything | nothing | unaffected |
| Recover | whatever the last snapshot held | changes since that snapshot | replaced by the last snapshot |
| Update | files and logins | installed apps and packages | image replaced; the data volume is untouched |
| Reset | conversations — never stored on the computer | the whole volume, including logins | wiped, then scheduled for erasure |
Which failure you are looking at
When a bot's screen cannot open, the screen names one of five classes. Two of them are not yours to fix, and the product says so rather than offering you a control that would change nothing: their Try again is shown, greyed, with the reason beside it.
| Class | What the screen says | Does trying again help? |
|---|---|---|
| Not answering | The computer started but did not answer. It is being rebuilt. | Yes. Start at step 1. |
| No room just now | There was no computer available just now. | Yes. Wait a minute and start at step 1. |
| Secure storage | The computer could not open its secure storage, so it stopped before starting. Your files and logins are untouched. | No. This needs an operator. |
| Credentials | The computer refused this deployment's credentials. | No. This needs an operator. |
| No computer set up | This deployment cannot run a bot's computer at all. | No. The control is Set up a computer, which opens Settings → Computer. |
"Not answering" is also the honest answer when the cause is not known — the computer is not responding and nothing sharper has been recorded. It is never a guess at a cause.
-
Retry. Close whatever refused and try again — a screen that would not open, a task that failed. Most failures are transient and clear on their own. This step has no screen of its own: it repeats whatever action failed.
-
Restart the app. Close and reopen the browser tab, or quit and relaunch the desktop app. This clears a stuck client without touching the computer at all. This step has no screen of its own: it happens outside the product.
-
Check for an update. Open Settings → Updates and click Check for Updates in the top section. A client bug is sometimes already fixed in a newer build.
<!-- shot: lifecycle-and-recovery-03-phone.png | Settings → Updates, checking for a client update, on a phone --> <!-- shot: lifecycle-and-recovery-03-desktop.png | Settings → Updates, checking for a client update, on a desktop --> -
Recover. In Settings → Updates, under Your computer, click Recover. This rebuilds the computer from its last saved snapshot; confirm once you understand you may lose very recent changes. Reach for this when the computer will not respond and you do not know why.
<!-- shot: lifecycle-and-recovery-04-phone.png | The Recover confirmation, on a phone --> <!-- shot: lifecycle-and-recovery-04-desktop.png | The Recover confirmation, on a desktop --> -
Update. When a newer computer image is available, the same section shows an Update button in place of the up-to-date banner. Files and logins survive; installed apps and packages do not, because every bot shares one image.
<!-- shot: lifecycle-and-recovery-05-phone.png | The Update control, on a phone --> <!-- shot: lifecycle-and-recovery-05-desktop.png | The Update control, on a desktop --> -
Reset. Click Reset, then type
<!-- shot: lifecycle-and-recovery-06-phone.png | The Reset confirmation, on a phone --> <!-- shot: lifecycle-and-recovery-06-desktop.png | The Reset confirmation, on a desktop -->resetto confirm. This erases the whole volume — files, logins and installed apps — and there is no undo. Your conversations are not stored on the computer and are not affected.
A worked example
Reset asks you to type the word below, case-insensitively, before the button will confirm:
reset
What can go wrong
| What you see | Why | What to do |
|---|---|---|
Your computer is being set up. This can take a minute. | The computer has not finished provisioning for the first time. | Wait — the actions on this page are disabled until it is running. |
No computer runtime is set up for this deployment. Set COMPUTER_PROVIDER=docker and run botseon computer preflight to see what is missing, or run your bots’ computer on your own Fly.io account. | Self-hosted only: no computer provider is configured at all. | Follow the message — retrying does not help until a provider is configured. |
The computer provider refused the request. Try again in a few minutes. | The underlying provider (Fly.io or Docker) rejected the request. | Retry after a few minutes; if it keeps happening, try Recover. |
The computer provider has no capacity right now. Try again in a few minutes. | The provider is temporarily out of room to run the computer. | Retry after a few minutes. |
The computer started but could not be reached. Try again. | The computer came up but its own daemon never answered. | Retry; if it keeps failing, try Recover. |
Could not queue that. Try again. | Update, Recover or Reset failed to queue the job. | Try again; if it keeps happening, restart the app first. |
See also
Last verified against build 1c545f3.