Pause and resume

Pause is for a Service you expect to use again but do not want running right now. Tokay stops the process while keeping its code, Config, Secrets, deployment history, and data ready for the next time you need it.

Last updated October 14, 2026

AI agent? Start with llms.txt.

Pausing changes the runtime, not the setup

A paused Service stops doing work immediately. A web app stops serving requests, a scheduled job stops firing, and a background worker stops processing.

Tokay shows a paused Service in gray because the stop was intentional. It does not appear as an incident or trigger a failure alert. The Project's databases keep running, sibling Services keep using them, and the Service's persistent data stays in place.

Resume returns to the last working version

Resume starts the version that was running before the pause, so a rolled back Service stays on the version you chose. A web app passes its normal health checks before Tokay sends traffic to it again.

When the Project deploys automatically and new code arrived while the Service was paused, Resume starts the newest code instead, since nothing else would deploy it. Auto-deploy never resumes a paused Service on its own.

Deploy All leaves paused Services paused, unless every Service in the Project is paused, as after restoring the Project. Then it starts them on the newest code, except one paused on a rollback, which you resume on its own.

You do not need to reconfigure the Service unless you want to change it.

Pause and delete solve different problems

Pause means the Service should stop for now. Delete means you are finished with it.

Deleted Services go to Recently Deleted and can be restored for 30 days. See Deleting and restoring for what deletion stops immediately and what Tokay keeps for recovery.