docs/src/pages/docs/Miscellaneous/issue_codes.mdx

---
name: Issue Codes
menu: Miscellaneous
route: /docs/miscellaneous/issue-codes
index: 3
version: 1
---

# Issue Code Reference

This page lists issue codes that may be displayed in
Superset and provides additional context.

## Issue 1000

```
The datasource is too large to query.
```

It's likely your datasource has grown too large to run the current
query, and is timing out. You can resolve this by reducing the
size of your datasource or by modifying your query to only process a
subset of your data.

## Issue 1001

```
The database is under an unusual load.
```

Your query may have timed out because of unusually high load on the
database engine. You can make your query simpler, or wait until the
database is under less load and try again.

## Issue 1002

```
The database returned an unexpected error.
```

Your query failed because of an error that occurred on the database.
This may be due to a syntax error, a bug in your query, or some other
internal failure within the database. This is usually not an
issue within Superset, but instead a problem with the underlying
database that serves your query.

## Issue 1003

```
There is a syntax error in the SQL query. Perhaps there was a misspelling or a typo.
```

Your query failed because of a syntax error within the underlying query. Please
validate that all columns or tables referenced within the query exist and are spelled
correctly.

## Issue 1004

```
The column was deleted or renamed in the database.
```

Your query failed because it is referencing a column that no longer exists in
the underlying datasource. You should modify the query to reference the
replacement column, or remove this column from your query.

## Issue 1005

```
The table was deleted or renamed in the database.
```

Your query failed because it is referencing a table that no longer exists in
the underlying database. You should modify your query to reference the correct
table.

## Issue 1006

```
One or more parameters specified in the query are missing.
```

Your query was not submitted to the database because it's missing one or more
parameters. You should define all the parameters referenced in the query in a
valid JSON document. Check that the parameters are spelled correctly and that
the document has a valid syntax.

## Issue 1007

```
The hostname provided can't be resolved.
```

The hostname provided when adding a new database is invalid and cannot be
resolved. Please check that there are no typos in the hostname.

## Issue 1008

```
The port is closed.
```

The port provided when adding a new database is not open. Please check that
the port number is correct, and that the database is running and listening on
that port.

## Issue 1009

```
The host might be down, and cannot be reached on the provided port.
```

The host provided when adding a new database doesn't seem to be up.
Additionally, it cannot be reached on the provided port. Please check that
there are no firewall rules preventing access to the host.

## Issue 1010

```
Superset encountered an error while running a command.
```

Something unexpected happened, and Superset encountered an error while
running a command. Please reach out to your administrator.

## Issue 1011

```
Superset encountered an unexpected error.
```

Something unexpected happened in the Superset backend. Please reach out
to your administrator.

## Issue 1012

```
The username provided when connecting to a database is not valid.
```

The user provided a username that doesn't exist in the database. Please check
that the username is typed correctly and exists in the database.

## Issue 1013

```
The password provided when connecting to a database is not valid.
```

The user provided a password that is incorrect. Please check that the
password is typed correctly.

## Issue 1014

```
Either the username or the password used are incorrect.
```

Either the username provided does not exist or the password was written incorrectly. Please
check that the username and password were typed correctly.

## Issue 1015

```
Either the database is spelled incorrectly or does not exist.
```

Either the database was written incorrectly or it does not exist. Check that it was typed correctly.


## Issue 1016

```
The schema was deleted or renamed in the database.
```

The schema was either removed or renamed. Check that the schema is typed correctly and exists.