Invalid Deployment State Transition

invalid-deployment-state-transition · 409

The deployment can't be rolled back to, because it isn't a finished deployment that a newer one replaced.

A rollback runs an older deployment's image again, so the target must be superseded or rolled_back. from is the state the target is actually in, and nothing changed.

Besides the members every error carries, this type adds deploymentId, from and to.

Common causes

  • The target is the deployment that is running now.
  • The target never finished: it failed, was cancelled, or is still building or deploying.

How to fix the call

  • List the service's deployments and pick one whose status is superseded or rolled_back.
  • To ship the current code again, start a new deployment instead.
  • Don't retry the same rollback: the target's state won't change on its own.

Example response

json
{
  "type": "invalid-deployment-state-transition",
  "title": "Invalid Deployment State Transition",
  "detail": "Deployment '0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401' cannot move from 'running' to 'deploying'",
  "deploymentId": "0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
  "from": "running",
  "to": "deploying",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/deployments/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/rollback",
  "method": "POST",
  "instance": "POST /v1/deployments/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/rollback",
  "status": 409,
  "docs": "https://ghaym.me/docs/errors/invalid-deployment-state-transition"
}