Skip to main content
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.
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.

​
2XX - Unexpected Errors

These errors indicate unexpected conditions that require attention.

​
3XX - System Reliability Errors

​
System Components (31X)

​
Third-Party Dependencies (32X)

​
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.
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. 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.
See Get Help for every way to reach us.