# OL-4253 — Update apply failed (generic)
> Catch-all for any apply pipeline stage that failed in a way the more
> specific OL-codes don't capture. The running binary stays on the
> current version.
## When this fires
- A stage failed without a specific code (download network error,
filesystem error during extract, etc.).
- The daemon RPC observed a failure response and the in-process fallback
also could not complete.
## How to fix it
1. Check the CLI's stderr / `tracing` logs (`RUST_LOG=debug`) for the
`stage=` field — it identifies which step failed.
2. Match the stage to a more specific code:
- `download` → `OL-4252` (network).
- `extract` → likely a tar header issue; rare with npm tarballs.
- `verify` → `OL-4254`.
- `sanity` → `OL-4255`.
- `swap` → `OL-4256`.
3. Re-run `openlatch-provider update --apply --yes`. Most apply
failures are transient.
## Related
- `OL-4254`–`OL-4259` for stage-specific failure modes.
- `.claude/rules/auto-update.md` — pipeline overview.