Skip to content

Tenant Not Eligible For A Custody Move

URI: https://docs.ankatech.co/errors/custody-move-tenant-not-eligible
HTTP Status: 409 Conflict

When you see this

A key custody move, or a key-encryption key rotation, was asked for a tenant whose lifecycle state does not admit one. Nothing was written.

A suspended or closed tenant's keys do not move. Suspension for non-payment, in particular, never moves custody: a suspended tenant keeps its key protection exactly as it was, including its own key management service. When a tenant with a scheduled window is suspended, the window is cancelled and the move returns to PENDING, ready to be scheduled again once the tenant is reactivated.

Response Example

{
  "type": "https://docs.ankatech.co/errors/custody-move-tenant-not-eligible",
  "title": "Tenant Not Eligible For A Custody Move",
  "status": 409,
  "detail": "The tenant's state does not admit a key custody move. Nothing was written.",
  "instance": "/api/v3/admin/platform/tenants/8f14e45f-ceea-467a-9575-0d5b2a1f3c11/key-custody/moves/5e2d4c6b-8a1f-4b3c-9d7e-0f1a2b3c4d5e/schedule",
  "timestamp": 1793696400,
  "extensions": {
    "requestId": "9c41e7a2-5b08-4d3f-a6e1-2f7c90b4d815"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details. The detail does not name the tenant's state.

How to Resolve

  1. Read the tenant's status. A suspended tenant is reactivated first; a closed tenant's custody never moves again.
  2. Schedule the move again after the reactivation.

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