Rolling Updates

When a Release is promoted, new Processes are gracefully rolled out to avoid disruption to the App.

How it Works

The rolling update proceeds in a “make one, break one” process in order to maintain Service uptime and capacity.

Minimum / Maximum configuration

Rolling updates will respect the deployment configuration to control the minimum number of healthy processes and maximum number of overall processes to have running at any one time during the update. This defaults to a minimum of 50% and a maximum of 200%.

Automatic Rollback

If any of the following conditions occur while the new Release is being rolled out, the rollout will reverse and return all Processes to the original Release:

Any of these issues will appear in the logs that display during the promotion to help you determine what is going wrong.

See Troubleshooting for some tips on diagnosing common failure cases.