Skip to content

Deployment Backend Restore Unavailable

URI: https://docs.ankatech.co/errors/deployment-backend-restore-unavailable
HTTP Status: 422 Unprocessable Entity

When you see this

A restore of the deployment key-protection backend credential was requested and there is no superseded credential to put back. The retained reference is written by a rotation and by nothing else, so a deployment whose credential has been established but never rotated has nothing to restore. Nothing was contacted, because there was nothing to prove, and the credential in effect is unchanged.

Common Causes

  • restorePrevious was submitted on a deployment whose credential has been established but never rotated.
  • A restore was submitted twice: the first one consumed the retained reference, leaving nothing behind it.

Response Example

{
  "type": "https://docs.ankatech.co/errors/deployment-backend-restore-unavailable",
  "title": "Deployment Backend Restore Unavailable",
  "status": 422,
  "detail": "There is no superseded deployment key-protection backend credential to restore. The credential in effect is unchanged.",
  "instance": "/api/v3/admin/platform/setup/backend/credential",
  "timestamp": 1730000000,
  "extensions": {
    "requestId": "b2609f47-1d5a-4c78-8e30-5f9a1c62d704"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.

How to Resolve

  1. Confirm the current credential state with GET /api/v3/admin/platform/setup/backend/configuration, which reports credential presence as a boolean.
  2. If you need a different credential in force, submit it as a credential value rather than as a restore — exactly one of credential and restorePrevious may be present.
  3. Treat this as a real refusal, not a no-op: the credential you were trying to recover is not in effect and the one already in force is unchanged.

For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.