Skip to Content

Query error reasons

Query timed out

The query ran too long and was stopped.

Reason in E1005Diagnostic codeWho can fix itDoes a retry help?
QUERY_TIMEOUTDBN-QRY-003The viewer, then your adminYes, 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

WhoMessageNext step
Admin or API callerThe query took too long and was stopped.Try a shorter date range or fewer groups.
Embed viewerThis took too long to load.Try a shorter date range.

How to fix it

  1. Use a shorter date range or a filter.
  2. Group by fewer columns.
  3. If it keeps happening, check the load on the warehouse.

Warehouse codes behind it

WarehouseCodes
MySQL, SingleStore3024, 1317
ClickHouse159 (TIMEOUT_EXCEEDED)
BigQuerytimeout
TrinoEXCEEDED_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.

On this page