query_rows_limit_exceeded

{
  "meta": {
    "requestId": "req_2c9a0jf23l4k567"
  },
  "error": {
    "detail": "Query attempted to read too many rows. Try adding more filters or reducing the time range.",
    "status": 422,
    "title": "Unprocessable Entity",
    "type": "/errors/user/unprocessable_entity/query_rows_limit_exceeded"
  }
}

​

Likely causes

• The query scans too much: a wide time range, few filters, or raw rows instead of an aggregate.

​

How to fix

1. Narrow the time range.
2. Filter on key ID, identity ID, namespace, or another indexed column.
3. Aggregate instead of selecting raw rows.
4. If you need every row in a large range, split it into smaller windows and run one query per window.

​

Related errors

• err:user:unprocessable_entity:query_memory_limit_exceeded: the query used too much memory or the result was too large.
• err:user:unprocessable_entity:query_execution_timeout: the query ran too long.
• err:user:bad_request:query_range_exceeds_retention: the time filter reaches past the retention window.