Skip to content

Log Search Rate Limited

URI: https://docs.ankatech.co/errors/log-search-rate-limited
HTTP Status: 429 Too Many Requests

When you see this

The caller has already made 30 platform log searches in the last minute. Nothing was searched and nothing was recorded in the audit trail. The limit is per caller and the window slides: a search is admitted again as soon as the oldest of those 30 is more than a minute old, and Retry-After states how many seconds that is. Each Admin API instance counts on its own.

Common Causes

  • A script that pages through a long window without pausing between pages.
  • Several browser tabs of the console's Logs page re-running the same search.

Response Example

{
  "type": "https://docs.ankatech.co/errors/log-search-rate-limited",
  "title": "Log Search Rate Limited",
  "status": 429,
  "detail": "Too many log searches by this caller in the last minute; nothing was searched. Retry after the time the Retry-After header states.",
  "instance": "/api/v3/admin/platform/logs",
  "timestamp": 1760348487,
  "extensions": {
    "requestId": "7c9e6679-7425-40de-944b-e07fc1f90ae7"
  }
}

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 search again.
  2. Narrow the search (a shorter window, a service, a level or a correlation id) so fewer pages are needed, or raise size up to 200 per page.

Operations that emit it

Method Endpoint
GET /api/v3/admin/platform/logs

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