Skip to content

Compliance Pack Not Found

URI: https://docs.ankatech.co/errors/compliance-pack-not-found
HTTP Status: 404 Not Found

When you see this

A request read one compliance pack definition by its identifier, and the identifier is well formed but names no pack of the running release. The Admin API answers it on both planes: GET /api/v3/admin/platform/compliance-packs/{packId} and GET /api/v3/admin/tenants/{tenantId}/compliance-packs/{packId}.

Common Causes

  • The identifier is misspelled, or uses a different case. Identifiers are upper case with underscores, for example BSI_TR_02102_1.
  • The identifier was taken from a licence issued under an earlier release, whose pack vocabulary was different. A licence may still name such an identifier; it resolves to no definition in this release, and there is no alias.
  • The identifier names a framework the platform does not define as a pack.

Response Example

{
  "type": "https://docs.ankatech.co/errors/compliance-pack-not-found",
  "title": "Compliance pack not found",
  "status": 404,
  "detail": "No compliance pack exists with the requested identifier.",
  "instance": "/api/v3/admin/platform/compliance-packs/NIST_SP_800_53",
  "timestamp": 1790661079,
  "extensions": {
    "requestId": "7c9e6679-7425-40de-944b-e07fc1f90ae7"
  }
}

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

The detail lists no identifier: the valid set is what the list operation returns, not what a refusal enumerates. An identifier that is not well formed at all (lower case, a hyphen, more than 64 characters) is refused earlier with 400 Validation Error, whose detail does not echo the value either.

How to Resolve

  1. List the packs of this release with GET /api/v3/admin/platform/compliance-packs (or the tenant-plane list) and use an identifier it returns.
  2. If the identifier came from a licence, the licence was issued with a pack vocabulary this release does not define. The licence stays valid; to have its packs resolve, have it re-issued with current identifiers and import the new licence. See Compliance Packs.

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