Skip to content
Install

Roll back an app

When a deploy goes wrong, a rollback puts the app back on an earlier image in the time it takes to start new pods, with no rebuild. A rollback is a deploy of the older image, so it uses the same rolling update and health checks as any other deploy.

A rollback does not revert your repository. It also leaves the database schema as it is, unless you restore bound databases.

  1. Open the app.
  2. Go to Activity.
  3. In History, find the release.
  4. Select Roll back. To return to the previous release, select Roll back on the Live release at the top of the page.
  5. (Optional) Select Also restore bound databases to before this deploy. Each database returns to its checkpoint from before the deploy.
  6. Select Promote.
  1. Roll back to the last working image.
  2. Fix the problem in the repository.
  3. Push the fix. If auto-deploy is on, Orchard builds and deploys it.

A restart creates new pods on the same image. Use it for a stuck process, such as a blocked connection pool. If the image has the problem, use a rollback instead.

Open the app and select Restart in the header.