MultiConnectCloud › Server Deployments
8. Grace periods and previous versions
A game session cannot move between containers. So when containers are replaced, the old ones are not cut off: they keep serving the players already on them for a grace period, and they keep billing while they run.
| Setting | Applies to | Choices |
|---|---|---|
| Grace Period | Containers replaced by a redeploy or plan change | None, 30 minutes, or whole hours from 1 hour to 24 hours |
| Scale-Down Grace Period | Workers removed by a scale or by autoscaling | Same as above, or the same choices |
During the grace period:
- New players should go to the new containers. Lookups never return a retiring container to a new client (Section 9), and the
generation.retiringwebhook tells your own backend which containers to stop using (Section 11). - The Connections panel marks each old container Draining with the time it retires.
Release old containers early
If your players have left the old servers before the grace period ends, remove them now and stop paying for them:
- On the deployment page, find Previous Versions. It lists each draining build version, its containers, when it retires and why.
- Click Release now on a version, then Release now again to confirm. Players still connected to those servers are disconnected.
Your backend can do the same with the release call in Section 9.
At most two previous generations can drain at once. While two are draining, a new redeploy, plan change or scale is refused until one is released or retires.

