Log Fingerprint Rate Bound Unavailable

URI: https://docs.ankatech.co/errors/log-fingerprint-rate-unavailable
HTTP Status: 503 Service Unavailable

When you see this

Every log fingerprint computation is counted against the caller's rate bound in a shared store before it runs. The counter could not be read, so the bound cannot be enforced and nothing was computed. The operation is refused rather than admitted without its bound. Retry-After states when to retry.

Common Causes

• The Admin API could not reach Redis, or Redis did not answer the counter update.

Response Example

{
  "type": "https://docs.ankatech.co/errors/log-fingerprint-rate-unavailable",
  "title": "Log Fingerprint Rate Bound Unavailable",
  "status": 503,
  "detail": "The rate bound of log fingerprint computations cannot be enforced right now, so nothing was computed. Retry later.",
  "instance": "/api/v3/admin/platform/log-fingerprints",
  "timestamp": 1761390000,
  "extensions": {
    "requestId": "8d1f3c7a-2e5b-4a96-b0c4-7f9e1a3d5b28"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details. The response carries Retry-After in seconds.

How to Resolve

1. Wait the number of seconds Retry-After states, then compute again.
2. If it persists, check Redis on the System Health page and the Admin API's readiness.

Operations that emit it

Related Errors

• Log Fingerprint Rate Limited (429) - the bound was read and is spent
• Log Fingerprint Audit Unavailable (503) - the computation could not be recorded in the audit trail

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