query_execution_timeout

{  "meta": {    "requestId": "req_4dgzrNP3Je5mU1tD"  },  "error": {    "detail": "Query exceeded the maximum execution time of 30 seconds",    "status": 422,    "title": "Unprocessable Entity",    "type": "https://unkey.com/docs/errors/user/unprocessable_entity/query_execution_timeout"  }}

What Happened?#

Your analytics query took too long to execute! We limit queries to 30 seconds to keep the analytics service responsive for everyone.

This usually happens when you're querying a large time range or complex data without enough filters.

How to Fix It#

1. Query Smaller Time Ranges#

The most common fix is to reduce the time range:

SELECT COUNT(*)FROM key_verifications_v1WHERE time >= now() - INTERVAL 1 YEARGROUP BY toStartOfDay(time)

2. Add More Filters#

Filter your data to reduce the amount of work the query needs to do:

SELECT key_space_id, COUNT(*) as totalFROM key_verifications_v1GROUP BY key_space_id

3. Use Aggregated Tables#

For historical data, use pre-aggregated tables instead of raw events:

SELECT  toStartOfHour(time) as hour,  COUNT(*) as totalFROM key_verifications_v1WHERE time >= now() - INTERVAL 30 DAYGROUP BY hour

4. Limit Result Size#

Add a LIMIT clause to stop processing once you have enough data:

SELECT key_space_id, COUNT(*) as totalFROM key_verifications_v1WHERE time >= now() - INTERVAL 7 DAYGROUP BY key_space_idORDER BY total DESCLIMIT 100

Need Longer Execution Time?#