Skip to content

Projection Signing Key Set Unreadable

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

When you see this

The platform read its stored projection signing key set and could not admit it. The custody root answered, so this is not an outage: the stored state itself is corrupted, foreign or incomplete, and a retry reads the same state and fails the same way. Nothing was changed.

It is distinct from the 503 answers of the same operations — projection-signing-key-custody-unavailable, projection-signing-key-set-not-initialized and backend-not-bound — which are transient.

Common Causes

  • The stored key-set document was altered or replaced outside the platform.
  • The stored document and its status no longer belong together.

Response Example

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

{
  "type": "https://docs.ankatech.co/errors/projection-signing-key-set-unreadable",
  "title": "Projection Signing Key Set Unreadable",
  "status": 500,
  "detail": "A stored projection signing key document could not be admitted",
  "instance": "/api/v3/admin/platform/projection-signing-keys",
  "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 answer does not change by itself.
  2. Escalate to the platform operator with the requestId. When only the stored status is affected, the next committed change to the key set rewrites it.

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.