SafeBump / update failures / unexpected-error
unexpected-errorunexpected-error: 61 reports, 14 still openWhat it means: An error with no specific reason code.
What to do: Check the Gateway logs and the saved failure context under logs/support/ in your state directory before retrying.
The OpenClaw maintainer answered similar reports: #168691, #158668, #152416, #152419. These replies usually list exactly what to collect and the known fix for your version.
Stuck on 2026.9.3 or 2026.9.4? The OpenClaw maintainer's own recipe (#165706) is one manual hop to the current release, then a Doctor pass: npm install -g [email protected] --allow-scripts=openclaw, then openclaw doctor --fix, then openclaw gateway restart. From 2026.9.8 onward, openclaw update handles the rest. On npm 11.15 or older, drop --allow-scripts=openclaw. Back up first with openclaw backup create --verify.
Before you retry, openclaw update status --json shows the unredacted failing step on your machine, and openclaw gateway status --deep shows what is actually serving. A retry overwrites that history.
Update Rescue: $149 fixed, and you only pay once it works
Gateway stuck in health: starting, a crash loop after openclaw update, Doctor refusing your workspace, memory or CPU running away, or a Telegram, WhatsApp or Discord channel gone silent. We get you back to a stable, pinned version with your sessions, memory and channels intact, then write down the pin and a safe update routine for your setup.
Would rather keep it private? Use email. A GitHub request is public, so don't paste secrets or logs that contain tokens there.
All reason codes · Is it safe to update? Per-release verdicts