Zero-downtime deployments
6 min readUpdated August 2026
A git deploy or a settings save rolls out a new revision while the previous pods stay up until the new ones pass health checks. You do not turn on a separate “zero downtime” flag.
Step by step
01
Set a health-check path
On Runtime, enable Health Checks and set Health Check Path to an HTTP endpoint on the container port that returns 200 when the app can take traffic. Also set Startup, Timeout, and Interval seconds.
02
Deploy as usual
Push the connected branch (if Autodeploy is on) or commit from the canvas. Traffic stays on the old revision until the new one is ready.
03
If the new revision is bad
Use Deployments → Instant Rollback (or Rollback Config) to go back. Restart only recycles the current revision — it is not a rollback.