> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/reference/error-codes.md).

# Error codes

Error codes returned by e6data, organized by component. Each page lists codes, meanings, and fixes.

When something goes wrong, e6data returns a structured error with a code, message, and (often) details. This section is the reference for what each code means and how to resolve it.

## Error categories

| Category                                                                         | When you'll see it                                |
| -------------------------------------------------------------------------------- | ------------------------------------------------- |
| [Catalog errors](/query-engine/reference/error-codes/catalog.md)                 | Catalog creation, refresh, or connection issues   |
| [Cluster errors](/query-engine/reference/error-codes/cluster.md)                 | Cluster lifecycle and execution issues            |
| [Connectivity errors](/query-engine/reference/error-codes/connectivity.md)       | Network, endpoint, and reachability issues        |
| [Data governance errors](/query-engine/reference/error-codes/data-governance.md) | Permission and policy enforcement                 |
| [General errors](/query-engine/reference/error-codes/general.md)                 | Platform-level errors not specific to a component |
| [Query editor errors](/query-engine/reference/error-codes/query-editor.md)       | SQL Editor-specific issues                        |
| [Query history errors](/query-engine/reference/error-codes/query-history.md)     | Run History retrieval and filtering               |
| [REST API errors](/query-engine/reference/error-codes/rest-api.md)               | REST API-specific errors                          |
| [User account errors](/query-engine/reference/error-codes/user-account.md)       | Authentication, profile, and account              |
| [Workspace errors](/query-engine/reference/error-codes/workspace.md)             | Workspace lifecycle and management                |

## Reading an error

Errors include three things:

* **Code** - a short, stable identifier (e.g., `CLUSTER_SUSPENDED`)
* **Message** - a human-readable summary
* **Details** - context-specific data when relevant

When opening a support ticket, include the code, message, and any IDs from the details.

## Common patterns

| Pattern          | Likely cause                                                            |
| ---------------- | ----------------------------------------------------------------------- |
| `*_NOT_FOUND`    | Resource doesn't exist, or your token doesn't have permission to see it |
| `*_TIMEOUT`      | Configured timeout exceeded; tune or retry                              |
| `RATE_LIMITED`   | Too many requests; back off                                             |
| `*_PROVISIONING` | Resource being created; wait                                            |
| `*_SUSPENDED`    | Resource is paused; resume or wait for auto-resume                      |

## See also

* [Reference home](/query-engine/reference/reference.md)
* [Limitations](/query-engine/reference/limitations.md) - known limits that might surface as errors


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.e6data.com/query-engine/reference/error-codes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.