Skip to content

Compliance Remediation Execution In Progress

URI: https://docs.ankatech.co/errors/compliance-remediation-execution-in-progress
HTTP Status: 409 Conflict

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) under a new Idempotency-Key while another execution of the same action is still running: that execution has no completion record and has not reached its deadline. One action runs at most once at a time, whatever the Idempotency-Key, so no key is stepped by two runs of that action at once. The guarantee is per action, not per key: a run of another action that names the same key is not refused here, and a key whose state that run already moved is SKIPPED_ALREADY_DONE. Nothing was reserved, nothing was called, no execution was recorded and no audit row was written.

A retry of the running execution with its own Idempotency-Key is answered 409 Idempotency Key In Progress instead.

See Compliance Remediation Plans — retrying safely.

Common Causes

  • The same person, or another session, confirmed the action twice, for example from two browser tabs or by pressing confirm again with a new key while the first run was still stepping keys.
  • An integration retried a confirmation that had not timed out on the server with a fresh Idempotency-Key instead of reusing the original one.

Response Example

{
  "type": "https://docs.ankatech.co/errors/compliance-remediation-execution-in-progress",
  "title": "Remediation Execution In Progress",
  "status": 409,
  "detail": "Another execution of this remediation action is still running; read the executions and preview again once it has completed.",
  "instance": "/api/v3/admin/tenants/3f2b8c1e-6d4a-4e7b-9a15-2c8d7e6f5a41/compliance-remediation/NSA_CNSA_2_0/actions/CNSA.ADMIT.GENERAL/executions",
  "extensions": {
    "requestId": "7c9e6679-7425-40de-944b-e07fc1f90ae7"
  }
}

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

How to Resolve

  1. Read the executions (GET …/compliance-remediation/{packId}/executions) and wait until the running one is COMPLETED or INTERRUPTED; a run is INTERRUPTED once its deadline passes without a completion record.
  2. Preview the step again: the completed run has probably changed the keys, so the old basis no longer matches.
  3. Confirm the new preview with a new Idempotency-Key. To retry the original request instead, reuse its original Idempotency-Key.

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