Skip to content

Custody Move In Progress

URI: https://docs.ankatech.co/errors/custody-move-in-progress
HTTP Status: 409 Conflict

When you see this

The tenant has an open key custody move — one that is scheduled or running — and the request would change something the move depends on. Nothing was changed by the request.

A key custody move re-wraps every key of the tenant under another key-encryption key. While one is open, the tenant's key protection is changed through the move's own operations only, and the tenant's lifecycle is held where the move needs it.

Common Causes

  • Starting a second custody move, or a key-encryption key rotation, for a tenant that already has an open one.
  • Declaring, binding, re-credentialing or reverting the tenant's own key management service (BYOK) while a move is scheduled or running, on either the platform or the tenant plane.
  • Assigning or clearing the tenant's Edition while a move is scheduled or running.
  • Activating, suspending, reactivating or closing a tenant that is in MAINTENANCE: a window move is re-wrapping its keys, and only the move leaves that state.

Response Example

{
  "type": "https://docs.ankatech.co/errors/custody-move-in-progress",
  "title": "Custody Move In Progress",
  "status": 409,
  "detail": "A key custody move is in progress for this tenant. Nothing was changed by this request. Retry once the move has finished or has been aborted.",
  "instance": "/api/v3/admin/tenants/8f14e45f-ceea-467a-9575-0d5b2a1f3c11/key-custody/moves",
  "timestamp": 1793696400,
  "extensions": {
    "requestId": "9c41e7a2-5b08-4d3f-a6e1-2f7c90b4d815"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details. The detail is fixed: it names neither the backends, the mode nor the actor of the move.

How to Resolve

  1. Read the tenant's key custody (GET /api/v3/admin/tenants/{tenantId}/key-custody, or GET /api/v3/admin/platform/tenants/{tenantId}/key-custody on the platform plane). Its openMove shows the move, its state and its progress.
  2. Wait for the move to finish, or withdraw it: a move that has not started is cancelled, a window that has not made the keys live on the destination is aborted.
  3. Repeat the request once the move is COMPLETED, ABORTED or CANCELLED.

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