Skip to content

Custody Lineage Not Current

URI: https://docs.ankatech.co/errors/custody-lineage-not-current
HTTP Status: 409 Conflict

When you see this

A re-wrap step asked to wrap under a key-encryption key version that the answering replica of the key service does not yet resolve as the tenant's active version. Each replica caches the tenant's key-encryption key lineage for a bounded time, so a replica can lag a rotation or a flip by up to that bound.

This problem is answered by the key service to the platform's own administration service while it drives a key custody move, one bounded re-wrap step per call. It is never answered to a browser, an SDK or an API client, so its instance names an internal call and is not reproduced here. An operator sees its effect on the move instead: the move's state on the tenant's key custody read, and the audit trail of the move.

Response Example

{
  "type": "https://docs.ankatech.co/errors/custody-lineage-not-current",
  "title": "Custody Lineage Not Current",
  "status": 409,
  "detail": "The requested key-encryption key version is not yet the active one here. Retry later.",
  "correlationId": "6a0c2f9e-3d71-4b58-8e24-c1f5a7d9b036",
  "timestamp": 1793696400
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details. The detail is fixed: it names no tenant, key, key-encryption key or count.

How to Resolve

  1. Nothing. The engine waits and asks again; once the replica's cache follows, the step proceeds.

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