Skip to content

Projection Signing Key Transition In Progress

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

When you see this

Only one change to the projection signing keys is committed at a time. Another change — an operator request, or the platform's own scheduled rotation or retirement — was committed between this request's read and its commit, so this request was refused and nothing was changed.

Common Causes

  • Two administrators acted on the key set at the same moment.
  • The platform's scheduler rotated or retired a key while the request was in flight.

Response Example

HTTP/1.1 409 Conflict
Content-Type: application/problem+json

{
  "type": "https://docs.ankatech.co/errors/projection-signing-key-transition-in-progress",
  "title": "Projection Signing Key Transition In Progress",
  "status": 409,
  "detail": "Another projection signing key transition committed first",
  "instance": "/api/v3/admin/platform/projection-signing-keys/actions/rotate",
  "timestamp": 1798596000,
  "extensions": {
    "requestId": "7c9e6679-7425-40de-944b-e07fc1f90ae7"
  }
}

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

How to Resolve

  1. List the keys again and check whether the change you wanted is still needed.
  2. If it is, repeat the request. There is no Retry-After: the new state is readable at once.

See Projection Signing Keys for the screen that lists, rotates and revokes these keys.

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