chesterdocs

#Withdraw a deployment

Withdrawing switches a development or production deployment off for new runs and removes its webhooks, while runs already started continue; it cannot be undone, only replaced by deploying again.

#What withdrawing changes

flowchart LR
  W["Withdraw"] --> N["No new runs:<br/>not in the catalog,<br/>not callable"]
  W --> H["Webhooks removed<br/>at the external system"]
  W --> U["Static URL stops<br/>for this deployment"]
  W -. "unchanged" .-> R["Runs already started<br/>continue to the end,<br/>open tasks can be completed"]

#Withdraw a process's deployment

  1. Open the process, tab Versions.
  2. Click Withdraw next to Production or Development.
  3. Confirm in Deactivate deployment. with Deactivate.

"Deployment deactivated successfully" confirms it.

For an agent, Withdraw on its Deployments tab acts at once, without asking.

#What happens

  • The deployment starts nothing new: a production process disappears from the catalog, and call activities can no longer find it.
  • Its start webhooks are removed at the external system. If that fails, Chester tries again at its next restart.
  • Runs that already started are not stopped. They finish on the version they started with, and their open user tasks can still be completed. To stop one, cancel it in monitoring.

❌ A withdrawal cannot be undone. Deploy again — that deploys the current saved process, not the one you withdrew.

⚠️ If the server does not confirm the withdrawal, a warning says the deployment may keep running until a restart. The message is German.

#Deleting is not withdrawing

Deleting a process, a process group, an area or a project does not withdraw its deployments. Their webhooks and static URLs stay live until Chester restarts. Withdraw first, then delete.

⚠️ The delete confirmation only warns about production deployments.

⚠️ Deleting an agent says its running instances "will be terminated". They are not stopped.