SafeBump / update failures / managed-service-preflight
managed-service-preflightmanaged-service-preflight: 36 reports, 18 still openWhat it means: The updater refused before swapping packages because a check on the managed Gateway service failed.
What to do: 2026.9.4 updaters can refuse here before the target code ever runs. The fix is to use the manual procedure with the same package manager and prefix. On macOS, if /update or update.run failed with "running inside the gateway process tree", run openclaw update once from a separate Terminal.
The OpenClaw maintainer answered similar reports: #153990, #158352, #158231, #167712. 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 openclaw@2026.9.8 --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