Skip to main content
Settings > Updates lists the last five releases for a channel (stable, beta, or both), each with a compatibility verdict against your database. Pick one to see exactly what a rollback would do. The dashboard never applies it: the control plane does not replace its own binary, so you run the rollback on the server.

​
What the verdict means

​
From the CLI

​
Applying on the server

Releases your host kept (the last three it ran) roll back immediately, with no network needed:
A release the host does not have is staged first, with checksum and signature verification:
The rollback takes a fresh backup, stops the service, swaps the binary, starts it and waits for health and readiness. If the target is not healthy within --timeout (default 90s), the previous release is put back automatically and the command tells you so. Every attempt is written to the audit log.

​
When a restore is required

The plan lists each local backup with its time and schema. Everything written after the chosen backup is lost. Your current database is kept beside it as levelrail.db.before-rollback-<time>. Without a service manager, pass --stop-cmd and --start-cmd.

​
After an upgrade or rollback

Settings > Updates > Verify runs the control plane’s own health checks and shows a pass or fail result with the failing checks listed.
Last modified on October 12, 2026