Skip to content

Compliance Remediation Step Not Applicable

URI: https://docs.ankatech.co/errors/compliance-remediation-step-not-applicable
HTTP Status: 422 Unprocessable Entity

When you see this

A tenant confirmed a step of a compliance remediation action (POST /api/v3/admin/tenants/{tenantId}/compliance-remediation/{packId}/actions/{actionKey}/executions) whose step is a valid step name but not one this action offers. Each control type maps to a fixed set of steps; for example, a CRYPTOPERIOD action offers SET_KEY_EXPIRY and ROTATE_KEY, never REVOKE_SUPERSEDED_KEY, and an evidence-integrity action offers none. Nothing was executed, no execution was recorded and no audit row was written.

See Compliance Remediation Plans — the catalogue.

Common Causes

  • A client sent a step taken from another action.
  • A DECISION action whose only remedy is guidance (evidence integrity, or replacing a key with a public-only import) was asked to execute a step.

Response Example

{
  "type": "https://docs.ankatech.co/errors/compliance-remediation-step-not-applicable",
  "title": "Remediation Step Not Applicable",
  "status": 422,
  "detail": "The remediation action does not offer the requested step.",
  "instance": "/api/v3/admin/tenants/6f1b2c4e-8a3d-4f7e-9c21-5b0d7e9a1f34/compliance-remediation/NIST_PQC_TRANSITION/actions/NIST.CRYPTOPERIOD/executions",
  "extensions": {
    "requestId": "c1e5a9b3-7d24-4f6e-8b0a-2f9d3c6e1a58"
  }
}

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

How to Resolve

  1. Read the plan (GET /api/v3/admin/tenants/{tenantId}/compliance-remediation/{packId}): each action lists the steps it offers.
  2. Preview one of those steps and confirm it.

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