> ## Documentation Index
> Fetch the complete documentation index at: https://docs.textql.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Chat Error Messages (Advanced)

> What to do when Ana shows you an error statement.

<Warning>The docs in this section are rather intricate and technical, and they focus mainly on how Ana works as opposed to how to set up TextQL or work with Ana. TextQL users without technical knowledge should feel free to skip this section, as the information here won't contribute to a better usage experience.</Warning>

This page documents all error messages you might encounter while using TextQL chat, along with explanations and suggested solutions.

### 1XX - Expected Errors

These errors occur during normal operation and usually indicate temporary conditions.

| Code | Name | Description | Solution |
| - | - | - | - |
| 101 | AT\_CAPACITY | System is currently at maximum capacity. | Please try again in a few minutes. |
| 103 | SANDBOX\_GONE | This chat session has expired. | Start a new chat session. |
| 104 | PREVIOUS\_ERROR | Chat is locked due to a previous error. | Start a new chat session. |
| 105 | SANDBOX\_OOM | Python environment is out of memory. | Try with a smaller dataset. |

### 2XX - Unexpected Errors

These errors indicate unexpected conditions that require attention.

| Code | Name | Description | Solution |
| - | - | - | - |
| 201 | UNKNOWN | An unexpected error occurred. | Try again or contact support if the issue persists. |
| 202 | UNEXPECTED | An unexpected error occurred. | Try again or contact support if the issue persists. |
| 203 | INVALID\_STATE | Chat is in an invalid state. | Start a new chat session. |
| 205 | YOU\_ARE\_OFFLINE | No internet connection detected. | Check your internet connection and try again. |
| 206 | FE\_HEARTBEAT\_TIMEOUT | Lost connection to TextQL. | Check your connection and try again. |
| 207 | MISSING\_RECENT\_DFS | Recent data frames are unavailable. | Try again or contact support if the issue persists. |
| 208 | SANDBOX\_ERROR | Python environment error occurred. | Try again or contact support if the issue persists. |
| 209 | TIMEOUT | Request timed out. | Try again or contact support if the issue persists. |

### 3XX - System Reliability Errors

#### System Components (31X)

| Code | Name | Description | Solution |
| - | - | - | - |
| 312 | SANDBOX\_UNAVAILABLE | Python environment is offline. | Try again in a few minutes. |
| 314 | ONTOLOGY\_UNAVAILABLE | Ontology service is offline. | Try again in a few minutes. |

#### Third-Party Dependencies (32X)

| Code | Name | Description | Solution |
| - | - | - | - |
| 321 | LLM\_PROVIDER\_UNAVAILABLE | Ana lost connection to the language model mid-response. This can also be triggered by uploading `.xlsx` files with complex templates or a large number of sheets. | Start a new chat and try again. If you were uploading a file, try simplifying it (remove extra sheets or formatting) or split your request into smaller steps. Contact support if the issue persists. |

## Still stuck?

Most 3XX errors are connectivity or service failures, which are exactly the class of problem a network trace resolves fastest.

One exception: if you hit 321 while uploading an `.xlsx` file, the cause is usually the file itself rather than the connection. Follow the solution in the table above — retry in a new chat, simplify the workbook, or split the request — before recording a trace.

<Tip>
  **Bugs reported with a HAR file get resolved faster.** A network trace shows the exact request that failed — its status, timing, headers, and payload — so our engineers can pinpoint the failure instead of inferring it from a description and trying to reproduce it blind. For loading, timeout, and network errors it is often the difference between a fix and a round of follow-up questions.

  See [how to record and send one](/core/get-started/har-file). Uploading through the in-app **?** form strips the standard credential headers and parsed cookie arrays — but not tokens in non-standard headers, URLs, request bodies, or response bodies. **Review the file before you upload it.**
</Tip>

See [Get Help](/core/get-started/customer-support) for every way to reach us.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.