Query error reasons
Query error reasons
What each reason in an E1005 query error means, and who can fix it
When a chart, an embed or the API cannot get data, the error has the code E1005 and a
details.reason that names the cause:
{
"code": "E1005",
"message": "The data source did not answer in time.",
"hint": "Ask your admin to check that the warehouse is running and reachable.",
"details": {
"reason": "DATASOURCE_TIMEOUT",
"errorCode": "DBN-WH-007",
"retryable": true,
"ref": "A1B2C3"
}
}reasonis the cause. Use it in code to decide what to show.errorCodeis the diagnostic code, with its own page.retryableistruewhen the same request can work on a later try.reffinds the log line in Settings > Diagnostics > Logs.
Embed viewers never see host, user or table names. They see a short message and, for causes only an admin can fix, “This chart has a data setup problem.” The admin text stays on the error.
Reasons
| Reason | Name | What this means | Diagnostic code |
|---|---|---|---|
DATASOURCE_UNREACHABLE | Datasource unreachable | Databrain could not open a connection to your warehouse. | DBN-WH-001, DBN-WH-003 |
DATASOURCE_TIMEOUT | Datasource timed out | Your warehouse did not answer in time. | DBN-WH-007 |
AUTH_FAILED | Warehouse login rejected | Your warehouse rejected the user name, password or key that Databrain signs in with. | DBN-WH-002 |
PERMISSION_DENIED | Permission denied | The Databrain user in your warehouse cannot read a table that the query uses. | DBN-WH-005 |
SCHEMA_TABLE_NOT_FOUND | Table or column not found | A table or column that the query reads is not in your warehouse. | DBN-QRY-002 |
DATABASE_NOT_FOUND | Database not found | The database named in the datasource settings is not in your warehouse. | DBN-WH-008 |
DATASOURCE_NOT_FOUND | Datasource not found | The datasource of this metric no longer exists in Databrain. | DBN-CFG-006 |
QUERY_INVALID | Query syntax error | Your warehouse could not run the query because the SQL has a syntax error. | DBN-QRY-001 |
QUERY_TIMEOUT | Query timed out | The query ran too long and was stopped. | DBN-QRY-003 |
QUEUE_TIMEOUT | Query engine busy | The query engine was busy, so the query did not start. | DBN-SYS-001 |
DATASOURCE_BUSY | Datasource busy | Your warehouse was busy or refused the query because a limit was reached. | DBN-WH-004 |
RESULT_TOO_LARGE | Result too large | Your warehouse refused to return the result because it is too large. | DBN-WH-009 |
LIMIT_EXCEED | Result over the Databrain limit | The result is larger than Databrain returns for one chart. | DBN-QRY-004 |
UNRESOLVED_VARIABLE | Variable with no value | The SQL of the metric has a variable that has no value. | DBN-CFG-002 |
TABLE_APP_FILTER_NOT_APPLIED | Table filter not applied | A table filter from the guest token could not be applied, so the query did not run. | DBN-TEN-202 |
QUERY_REFUSED | Query refused | Databrain did not run the query. | DBN-CFG-002 |
SERVICE_UNAVAILABLE | File query service down | Databrain’s file query service, which runs queries on Amazon S3 and CSV datasources, did not answer. | DBN-SYS-001 |
HASURA_TIMEOUT | Databrain service timed out | A Databrain service took too long to answer. | DBN-SYS-001 |
| No reason | Unknown cause | Databrain does not know the cause. The message is “An error occurred while fetching data from the database.” | DBN-SYS-000 |
An error with no reason still has a ref. Search for it in Settings > Diagnostics > Logs, or
send it to support.