Custody Move Past Its Swap
URI: https://docs.ankatech.co/errors/custody-move-forward-only
HTTP Status: 409 Conflict
When you see this
An abort was asked of a key custody move that can only complete. Nothing was changed.
A window move can be aborted while it drains, prepares and verifies: the tenant then reopens on its unchanged source, with its keys, backend and key-encryption keys exactly as before. Once the swap has made the tenant's keys live on the destination, the move recovers forward only: every later step is repeated until it succeeds, and the tenant reopens on the destination. An online move (a key-encryption key rotation or a key change under the same provider account and credential) re-wraps keys in place while cryptographic operations continue and is never aborted either.
Response Example
{
"type": "https://docs.ankatech.co/errors/custody-move-forward-only",
"title": "Custody Move Past Its Swap",
"status": 409,
"detail": "The key custody move has made the tenant's keys live on the destination and can only complete. Nothing was changed.",
"instance": "/api/v3/admin/tenants/8f14e45f-ceea-467a-9575-0d5b2a1f3c11/key-custody/moves/5e2d4c6b-8a1f-4b3c-9d7e-0f1a2b3c4d5e/abort",
"timestamp": 1793696400,
"extensions": {
"requestId": "9c41e7a2-5b08-4d3f-a6e1-2f7c90b4d815"
}
}
Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.
How to Resolve
- Let the move complete. Its progress is on the tenant's key custody read.
- To return to the key-encryption key the tenant left, roll back once the move has completed:
POST .../key-custody/rollbackschedules a window move back to it while it is retained (30 days after the move that left it).
Related Errors
- Custody Roll Back Unavailable (409) - the key-encryption key a roll back would return to is no longer retained
- Custody Move State Conflict (409) - the move has already finished
For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.