Token Signing Key Transition In Progress

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

When you see this

A rotation or a revocation of the user-token signing key set lost a race: every transition is a compare-and-set on the stored set, and another transition committed between this request's read and its commit. Nothing was changed by this request.

Common Causes

• The platform's rotation scheduler committed a transition at the same moment. It runs every 60 seconds on every admin-api replica and initializes the set, retires an expired PREVIOUS key, or rotates when the ACTIVE key reaches the configured rotation period.
• Another administrator rotated or revoked at the same time.

Response Example

{
  "type": "https://docs.ankatech.co/errors/transition-in-progress",
  "title": "Token Signing Key Transition In Progress",
  "status": 409,
  "detail": "Another token signing key transition committed first",
  "instance": "/api/v3/admin/platform/token-signing-keys/actions/rotate",
  "timestamp": 1798596000,
  "extensions": {
    "requestId": "e4d1a8c2-6b3f-4a70-9d25-1f8c7b3e5a96"
  }
}

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

There is no Retry-After: the set has changed, so the request must be decided again, not repeated.

How to Resolve

1. Read the set again with GET /api/v3/admin/platform/token-signing-keys.
2. Decide whether the rotation or revocation is still wanted against the new set. A revocation names the key's current state as expectedState.

See Admin API — Platform Token Signing Keys^*.

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