query_execution_timeout

{
  "meta": {
    "requestId": "req_2c9a0jf23l4k567"
  },
  "error": {
    "detail": "Query execution time limit exceeded. Try simplifying your query or reducing the time range.",
    "status": 422,
    "title": "Unprocessable Entity",
    "type": "/errors/user/unprocessable_entity/query_execution_timeout"
  }
}

​

Likely causes

• The time range is too wide.
• The query reads a raw table when a rollup would do.
• The query filters late, or pulls raw rows instead of aggregating.

​

How to fix

• Narrow the time range first. A shorter range reads fewer rows.
• Query a rollup table (per-minute, per-hour, per-day) instead of the raw table when you don’t need individual events.
• Filter early on identifiers such as key ID, identity ID, or namespace before grouping.
• Aggregate in the query instead of pulling raw rows and aggregating on your side.
• Split long ranges into several queries by day or week and combine the results.

​

Related errors

• err:user:unprocessable_entity:query_rows_limit_exceeded: the query read or returned too many rows.
• err:user:unprocessable_entity:query_memory_limit_exceeded: the query used too much memory or the result was too large.
• err:user:bad_request:request_timeout: the whole request hit the API deadline.