Roll back

A site can always go back to the previous Release, unless the release notes say it cannot. The notes of Release 5.0.0 have no such exception.

Roll backCopy Anchor Link

awhere rollback

The command first runs the previous Release's Preflight against the current data. If it passes, it changes the containers back to the previous Release. If a check fails, the system changes nothing.

When you cannot go backCopy Anchor Link

A contract Migration changes data so that the older Release can no longer read it. If a newer Release has already run such a Migration on the data, you cannot go back. Preflight stops before it touches any container, and shows a message like this.

database `datastore` has Migration `<id>`, applied by release 5.1.0 on 2026-10-18; this node is release 5.0.0 and cannot read data after it. Run release 5.1.0 or newer.

In this case the only way back is to restore from a backup. The release notes say which Release has a contract Migration.

Restore from a backupCopy Anchor Link

1. Stop the whole site.
2. Restore the four databases and the env files from the backup you made before the upgrade. Data created after that is lost. You do not need to restore awhere-tiles, because the system rebuilds it.
3. Deploy the old Release with awhere upgrade, such as awhere upgrade 5.0.0.

What a rollback does not undoCopy Anchor Link

An expand Migration adds data without breaking the older Release. The data it added stays, but the older Release does not use it, so it has no effect. An older node may write the log line stream name already in use with a different configuration, which is harmless. To go from 5.0.0 back to v4, see Upgrade from v4.