Skip to content

Security Alert Already Acknowledged

URI: https://docs.ankatech.co/errors/security-alert-already-acknowledged
HTTP Status: 409 Conflict

When you see this

The security alert was already acknowledged. The first acknowledgment — who acknowledged it, when, and its note — is kept, and nothing was changed.

Common Causes

  • Two administrators acknowledged the same alert at nearly the same time.
  • The alert list was not refreshed after an earlier acknowledgment.

Response Example

{
  "type": "https://docs.ankatech.co/errors/security-alert-already-acknowledged",
  "title": "Security Alert Already Acknowledged",
  "status": 409,
  "detail": "This security alert is already acknowledged; the first acknowledgment is kept. Nothing was changed.",
  "instance": "/api/v3/admin/tenants/8d2f1c4e-3b7a-4e91-a6d5-0c9f2e8b7a14/security-alerts/5c9e2f14-8b3a-4d71-9e6c-2a1f7d0b4e83/acknowledgment",
  "timestamp": 1760951700,
  "extensions": {
    "requestId": "4e2a9c71-0b3d-4f58-a6e1-9d7c2b5f8e30"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details. This is an Admin API body, so the correlation identifier is extensions.requestId; see Error Index & Overview.

How to Resolve

  1. Reload the alert list with status=ACKNOWLEDGED or ALL to read who acknowledged it and the note.
  2. Nothing else is needed: an alert is acknowledged once.

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