Skip to content

Compliance Evidence Package Busy

URI: https://docs.ankatech.co/errors/compliance-evidence-package-busy
HTTP Status: 503 Service Unavailable

When you see this

A tenant requested a compliance evidence package (GET /api/v3/admin/tenants/{tenantId}/compliance-evidence/{packId}/package), and the Admin API instance that received the request was already preparing as many packages as it admits at once. Each instance prepares one package at a time: the whole package is prepared before its first byte is sent, because its audit row carries the SHA-256 of the whole archive.

It is a refusal, not a failure of the evidence. The request was refused at once, without waiting: after the tenant and the pack identifier were checked and before anything was read from the licence server. Nothing was evaluated, rendered, signed or recorded, and no audit row was written. The response carries Retry-After: 15, about the time one package at the bound takes to prepare.

It is this instance declining work whose memory it cannot bound, not a limit on the caller's request rate, which is why it is a 503 and not a 429. Downloading the signed document on its own (exportComplianceEvidence) renders no report and is never refused this way.

Common Causes

  • Another package for any tenant of the deployment was being prepared on the same Admin API instance.
  • Several downloads of the package were started at once, for example by a retry loop that does not honour Retry-After.

Response Example

{
  "type": "https://docs.ankatech.co/errors/compliance-evidence-package-busy",
  "title": "Compliance Evidence Package Busy",
  "status": 503,
  "detail": "Too many compliance evidence packages are being prepared on this instance; nothing was issued. Retry after the time the Retry-After header states.",
  "instance": "/api/v3/admin/tenants/3f2b8c1e-6d4a-4e7b-9a15-2c8d7e6f5a41/compliance-evidence/NIST_PQC_TRANSITION/package",
  "timestamp": 1790748600,
  "extensions": { "requestId": "7c9e6679-7425-40de-944b-e07fc1f90ae7" }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details. The detail is the same for every tenant, pack and caller.

How to Resolve

  1. Wait for the number of seconds the Retry-After header states, then request the package again. The admin console shows that wait beside the download button.
  2. Do not run package downloads in parallel. They are prepared one at a time per instance; a client that needs several packs requests them one after another.
  3. Do not read this as a statement about the evaluation or the licence: nothing was read, so it says nothing about whether the pack is licensed or the evidence can be issued.

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