Sometimes you need to quickly revert a change to your service, and don’t want to wait for a full build cycle of pushing a new commit and waiting for a new build. When you already have a previous deploy you wish to make live again, Render lets you quickly roll back to that deploy.Rollbacks for cron jobs are coming soon.
- Go to the Events tab for your service. Find the successful deploy you wish to roll back to, and click
Deploy to go to the deploy’s page.
If the deploy was successful and is not the current deploy for your service, you will see a Rollback to this deploy button. Click that button, confirm the rollback, and you will be redirected to your new rollback deploy. The build step will be skipped, and the deploy will begin immediately.
If automatic deploys are enabled for your service, rolling back to an old deploy will turn off Auto Deploy. It can be enabled again on your service’s Settings tab.
Some configuration for the service will be rolled back, but some will not.
|Health check path|
|Number of instances|
|Environment groups||See Environment Groups|
|Disks||Disks are stateful between deploys, and cannot be rolled back|
|Plan||If a previous deploy requires a larger plan, consider changing your service’s plan before rolling back|
|Redirects & Rewrites|
|Owner||If a service has been migrated to a Team from an individual User since the original deploy, the new deploy will belong to the team|
Environment groups are designed to provide a common source of configuration for multiple services. Therefore, rollbacks will not roll back to the original value of environment group variables, but will only roll back the list of linked environment groups. The most recent value for variables defined in the groups will be used. Any deleted environment groups will be ignored.Rollbacks skip the build step, so any use of environment group variables in the build process will not be reflected in the new deploy.
A rollback will only change configuration for the rollback deploy and will not change the service’s configuration. Any deploys that are not rollbacks will continue to use the latest configuration from a service.