Query error reasons
Databrain service timed out
A Databrain service took too long to answer.
Reason in E1005 | Diagnostic code | Who can fix it | Does a retry help? |
|---|---|---|---|
HASURA_TIMEOUT | DBN-SYS-001 | Databrain | Yes |
What this means
A Databrain service took too long to answer. Databrain could not read its own settings for the query in time, for example the datasource credentials. Your warehouse was not the cause.
What people see
| Who | Message | Next step |
|---|---|---|
| Admin or API caller | Databrain took too long to answer. | Try again in a minute. |
| Embed viewer | The data can’t be loaded right now. | Try again in a minute. |
How to fix it
- Try again in a minute.
- If it keeps happening, ask for help with the ref.
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.