Refresh Cooldown Active

URI: https://docs.ankatech.co/errors/refresh-cooldown
HTTP Status: 429 Too Many Requests

When you see this

You requested a snapshot refresh while a cooldown from a previous refresh is still active. Refreshes are rate-limited to protect the aggregation pipeline.

Common Causes

Triggering a refresh again before the cooldown period elapsed.
Multiple clients requesting refreshes within the same cooldown window.
An automated job refreshing more frequently than the cooldown allows.

Response Example

{
  "type": "https://docs.ankatech.co/errors/refresh-cooldown",
  "title": "Refresh Cooldown Active",
  "status": 429,
  "detail": "A refresh cooldown is active. Retry after the cooldown period elapses.",
  "instance": "/api/v3/audit/platform/stats/refresh",
  "correlationId": "550e8400-e29b-41d4-a716-446655440000",
  "timestamp": 1730000000
}

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

How to Resolve

Wait for the cooldown to elapse — check the Retry-After header for the remaining time.
Avoid triggering refreshes more frequently than the cooldown permits.
Rely on the scheduled refresh cycle instead of manual refreshes where possible.

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