Skip to Content

Query error reasons

Datasource busy

Your warehouse was busy or refused the query because a limit was reached.

Reason in E1005Diagnostic codeWho can fix itDoes a retry help?
DATASOURCE_BUSYDBN-WH-004Your adminYes

What this means

Your warehouse was busy or refused the query because a limit was reached. The warehouse hit a quota, a rate limit, a memory limit or its connection limit. A deadlock or a serialization conflict that the warehouse ended by failing this query also uses this reason.

What people see

WhoMessageNext step
Admin or API callerThe data source is busy or hit a limit.Try again in a minute. If it keeps happening, ask your admin to check the warehouse plan, quotas or concurrency.
Embed viewerThe data source is busy right now.Try again in a minute.

How to fix it

  1. Try again in a minute.
  2. If it keeps happening, check the plan, the quotas and the connection limit of the warehouse.

Warehouse codes behind it

WarehouseCodes
MySQL, SingleStore1040, 1203, 1205, 1213
PostgreSQL, Redshift, CockroachDBSQLSTATE 53300, 53200, 40001, 40P01
ClickHouse241 (MEMORY_LIMIT_EXCEEDED), 202 (TOO_MANY_SIMULTANEOUS_QUERIES)
SQL Server, Microsoft Fabric1205
BigQueryquotaExceeded, rateLimitExceeded, jobRateLimitExceeded, resourcesExceeded
TrinoEXCEEDED_GLOBAL_MEMORY_LIMIT, EXCEEDED_LOCAL_MEMORY_LIMIT, QUERY_QUEUE_FULL
Athena, Amazon S3, CSVThrottlingException, TooManyRequestsException
Elasticsearches_rejected_execution_exception

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