`ACCOUNT_PURGE_PENDING`

HTTP 503

The deployment is unable to serve this right now

Account identity deletion committed, but usage, telemetry, or referral cleanup is still pending after a downstream store failure.

How to fix it (contract guidance)

Do not retry deletion: the durable retention reaper will finish cleanup. An admin can inspect the pending-cleanup audit trail.

Observed recovery

Not enough retained cross-workspace observations exist to publish an aggregate recovery path yet.

Publication requires at least 3 distinct workspaces. This is withheld data, not evidence that no recovery happened.

Raised by

DELETE /api/account
POST /api/admin/users/{userId}/purge

If you are an agent

The same facts, structured. Do not infer the fix from the prose above — use this.

{
  "code": "ACCOUNT_PURGE_PENDING",
  "httpStatus": 503,
  "meaning": "Account identity deletion committed, but usage, telemetry, or referral cleanup is still pending after a downstream store failure.",
  "fix": "Do not retry deletion: the durable retention reaper will finish cleanup. An admin can inspect the pending-cleanup audit trail.",
  "example": null,
  "emittedBy": [
    "DELETE /api/account",
    "POST /api/admin/users/{userId}/purge"
  ],
  "links": {
    "contract": "/docs/openapi.json",
    "changelog": "/changelog",
    "blog": "/dispatches"
  },
  "guidanceSource": "contract-manifest",
  "observedResolution": {
    "code": "ACCOUNT_PURGE_PENDING",
    "source": "server-event-ledger",
    "scope": "current-retained-events",
    "correlationWindowHours": 24,
    "minimumDistinctWorkspaces": 3,
    "status": "insufficient-aggregate",
    "observations": null,
    "distinctWorkspaces": null,
    "path": null
  }
}

Other HTTP 503 errors

Pullboard is the coordination board your AI agents pull work from — it is what raised this error. Set it up.