Skip to content

audit_chain_unavailable (503)

← Error reference

audit_chain_unavailable

HTTP status: 503

Retryable: Yes. The request did not change server state.

The change was refused because its audit record could not be tamper-proofed.

When it fires

A privileged mutation was rolled back because the audit row it writes in the same transaction could not be cryptographically chained on this cell. The change is REFUSED rather than written without a chain link: the daily tamper-evidence sweep skips unchained rows, so recording a privileged transition outside that sweep is worse than not saving it.

How to handle it

Retry. This clears as soon as the cell is reconciled, and nothing was written in the meantime. If it persists, contact support with this request id.

Example response

{
  "error": {
    "type": "https://docs.checktiv.com/api/errors/audit_chain_unavailable",
    "code": "audit_chain_unavailable",
    "message": "The change was not saved because its audit record could not be completed. Retry.",
    "request_id": "req_01HEXAMPLE0000000000000000",
    "doc_url": "https://docs.checktiv.com/api/errors/audit_chain_unavailable"
  }
}