Query error reasons
Query timed out
The query ran too long and was stopped.
Reason in E1005 | Diagnostic code | Who can fix it | Does a retry help? |
|---|---|---|---|
QUERY_TIMEOUT | DBN-QRY-003 | The viewer, then your admin | Yes, with a smaller query |
What this means
The query ran too long and was stopped. The query started but did not finish in the time allowed. If your install limits how many queries can run at once on a datasource, a query that waits in line too long also ends with this reason.
What people see
| Who | Message | Next step |
|---|---|---|
| Admin or API caller | The query took too long and was stopped. | Try a shorter date range or fewer groups. |
| Embed viewer | This took too long to load. | Try a shorter date range. |
How to fix it
- Use a shorter date range or a filter.
- Group by fewer columns.
- If it keeps happening, check the load on the warehouse.
Warehouse codes behind it
| Warehouse | Codes |
|---|---|
| MySQL, SingleStore | 3024, 1317 |
| ClickHouse | 159 (TIMEOUT_EXCEEDED) |
| BigQuery | timeout |
| Trino | EXCEEDED_TIME_LIMIT |
Ask for help
Every error has a six-character ref, for example Ref A1B2C3. API callers find it in
details.ref. Search for the ref in Settings > Diagnostics > Logs to see the full log line, or
send the ref and the time of the error to support.