HelpReleasing

Go back to an earlier release

Put an earlier version back live, and choose whether its data goes back too. We show exactly what would be lost first.

If a release causes problems, open Releases and choose "Go back" on an earlier one. You get two choices:

  1. Keep today's data (recommended): the earlier version goes back live with all the data your users added since. This is right almost every time.
  2. Also put the data back: the database returns to the backup taken just before the release. Anything your users added or changed since is lost, so we list how many records in each table would go before you confirm, and keep a safety backup of today's data either way.
Technical detail

Code-only rollback redeploys the earlier release's image against the current database. With data, the worker first redeploys, then restores the pre-migration backup (release.backup_id) after taking a safety backup.