Quorum Request Not Pending

URI: https://docs.ankatech.co/errors/quorum-request-not-pending
HTTP Status: 409 Conflict

When you see this

The request is no longer pending, so it can no longer be approved, rejected or cancelled. Its status travels in extensions.status: EXECUTED, FAILED, REJECTED, CANCELLED or EXPIRED. Expiry is computed on read: a pending request whose expiresAt has passed reads EXPIRED even though no job ran.

Quorum (M-of-N) approval is described in Quorum Approval^*.

Common Causes

• Another approver's approval reached the quorum first and the operation ran.
• Another approver rejected it, or its requester cancelled it.
• It waited longer than the policy's requestTtlHours.

Response Example

{
  "type": "https://docs.ankatech.co/errors/quorum-request-not-pending",
  "title": "Quorum Request Not Pending",
  "status": 409,
  "detail": "This quorum request is EXPIRED and can no longer be approved, rejected or cancelled.",
  "instance": "/api/v3/admin/tenants/7d2f4a10-9c31-4b8e-a5d6-2f11c0b47e93/quorum/requests/9b1c2d3e-4f5a-4b6c-8d7e-0f1a2b3c4d5e/approve",
  "timestamp": 1730000000,
  "extensions": {
    "status": "EXPIRED",
    "requestId": "550e8400-e29b-41d4-a716-446655440000"
  }
}

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

How to Resolve

1. Read extensions.status.
2. EXPIRED or REJECTED: if the change is still wanted, its requester asks for it again.
3. FAILED: read the request's failureType and failureDetail; the operation itself refused when it ran.

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