Skip to content

Projection Signing Key Transition Refused

URI: https://docs.ankatech.co/errors/projection-signing-key-transition-refused
HTTP Status: 500 Internal Server Error

When you see this

The platform computed the key set that a rotation or revocation would produce and its own invariants refused it — for example a set without exactly one ACTIVE and one NEXT key. This is a defect of the server, not a conflict the caller can resolve. The refusal happens before anything is stored: the key set is unchanged.

Common Causes

  • A server defect in the requested transition. It is not transient.

Response Example

HTTP/1.1 500 Internal Server Error
Content-Type: application/problem+json

{
  "type": "https://docs.ankatech.co/errors/projection-signing-key-transition-refused",
  "title": "Projection Signing Key Transition Refused",
  "status": 500,
  "detail": "The projection signing key transition would break a key-set invariant",
  "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. Do not retry in a loop: the same request is refused the same way.
  2. Escalate to the platform operator with the requestId.

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.