Skip to main content
Pausing scales one service to zero replicas and leaves everything else in place: its config, image, disks, secrets and public host all stay. Coming back needs no rebuild. Pause is set per service, so you can pause a background worker while its web sibling keeps serving.

Pause and start

On the service’s page, next to Deploy: Pause is a live action rather than saved configuration. The next deploy, whether from a push or a manual Deploy, brings the service back up. Pause a service to stop it now; redeploy when you want to resume the normal lifecycle. Databases pause the same way: the cluster hibernates with its disk and credentials intact, and Start brings it back with the same data. Static sites have nothing running, so they have no Pause.

Pausing a cron job

A cron job (type: cron) has no resident pods, so Pause stops its schedule instead. While it is paused, no scheduled runs start, the job’s Overview shows it as paused in place of its next run, and its run history stays as it was. A run that was already in progress when you paused finishes normally. Unlike pausing other services, a cron pause survives deploys: a push does not resume a job you stopped. Start resumes it from the next scheduled slot, and the slots missed while it was paused are not run. Run now still works while it is paused.
Pausing a service that others depend on breaks those siblings while it is down. Pause leaf services, or pause a group together.

Auto-pause on a timer

To shut a service down after it has been running for a while, set an auto-pause schedule from the Deploy menu. This suits a demo that should stop itself, or a service you do not want billing overnight.
  • Pick a duration. The service scales to zero once it has been continuously live that long.
  • The clock measures uptime since the last rollout, so a deploy or a manual Start resets it and a freshly deployed service always gets its full window.
  • Nothing is destroyed. A deploy or Start brings it back and restarts the timer.
  • Set the value to 0 to turn the schedule off.

Auto-pause or sleep

Both scale a service to zero, and a service can use one or the other, never both. Choose auto-pause when you want something to stop and stay stopped. Choose sleep when you want it to come back by itself. Cron services have no resident pods, so neither applies to them. To stop a cron job, pause it as described in Pausing a cron job.