# Frequently Asked Questions ## Common error codes * **4xx (client error status codes)**: generally request syntax errors, authentication failures, or authorization failures, etc., where the request cannot be completed. * **5xx (server error status codes)**: generally server-side errors, such as server downtime, request processing timeout, etc. | Error code | Possible cases | Solution | | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **400** | Request body format error, etc. |

Check the error content returned by the conversation or the console\

\[Common case 1]: if it is a Gemini model, card binding may be required;
\[Common case 2]: data size exceeds the limit, commonly seen in vision models; if the image size exceeds the upstream single-request traffic limit, this error code will be returned;
\[Common case 3]: unsupported parameters were added or parameter values were entered incorrectly. Try creating a new clean assistant to test whether it works normally;
\[Common case 4]:the context exceeds the limit; clear the context, create a new conversation, or reduce the number of context turns.

| | **401** | Authentication failed: the model is not supported or the service provider account is banned, etc. | Contact or check the account status of the corresponding service provider | | **403** | No permission for the requested operation | According to the error message returned by the conversation or[console](#kong-zhi-tai-bao-cuo-cha-kan-fang-fa)error prompt to take appropriate action | | **404** | Requested resource not found | Check the request path, etc. | | **422** | The request format is correct, but the semantics are incorrect | This kind of error can be parsed by the server, but it cannot be processed. It is commonly seen in JSON semantic errors (for example: null values; a value is required to be a string, but a number or boolean is used instead, etc.). | | **429** | Request rate limit reached | The request rate (TPM or RPM) has reached the limit; wait a while and try again | | **500** | Internal server error, unable to complete the request | If it keeps happening, contact the upstream service provider | | **501** | The server does not support the requested function and cannot complete the request | | | **502** | When a server acting as a gateway or proxy attempted to execute the request, it received an invalid response from the remote server | | | **503** | The server, due to overload or system maintenance, is temporarily unable to process the client's request. The length of the delay may be included in the server's Retry-After header. | | | **504** | The server acting as a gateway or proxy did not obtain a response from the remote server in time | | *** ## How to view console errors * Click the Cherry Studio client window and then press the shortcut key with + Shift + I(Mac:Command + Option + I) {% hint style="info" %} * The currently active window must be the Cherry Studio client window in order to open the console; * You need to open the console first, then click Test or initiate a conversation request to collect request information. {% endhint %} - In the pop-up console window, click `Network` → click the last item marked with a red `×` in section ② `completions`*(when errors occur in chat, translation, model connectivity checks, etc.)* or `generations`*(when errors occur in drawing)* → click`Response`to view the complete response content (the area marked ④ in the image). > If you cannot determine the cause of the error, please send a screenshot of this screen to [the official community group](https://t.me/CherryStudioAI) for help.
This checking method can obtain error information not only during conversations, but also during model testing, when adding knowledge bases, when drawing, etc. In any case, you need to open the debugging window first, then perform the request operation to obtain the request information. {% hint style="info" %} The name in the Name field (② in the image above) will differ depending on the scenario Conversation, translation, model check:`completions` Drawing:`generations` Knowledge base creation:`embeddings` {% endhint %} *** ## Formula not rendered / formula rendering error * If the formula is not rendered and the formula code is displayed directly, check whether the formula has delimiters > **Delimiter usage** > > *Inline formula* > > * Use a single dollar sign: `$formula$` > * or use`\(` and `\)`, for example:`\(formula\)` > > *Standalone formula block* > > * Use double dollar signs: `$$formula$$` > * or use `\[formula\]` > * Example: `$$\sum_{i=1}^n x_i$$`\ > $$\sum\_{i=1}^n x\_i$$ * Formula rendering error/garbled text is common when the formula contains Chinese text; try switching the formula engine to KateX. *** ## Unable to create knowledge base / failed to obtain embedding dimensions 1. Model status unavailable > Confirm whether the service provider supports this model, or whether the model service status of the service provider is normal. 2\. A non-embedding model was used *** ## The model cannot recognize images / cannot upload or select images First, confirm whether the model supports image recognition. For popular models, Cherry Studio will classify them; models with a small eye icon after the name support image recognition. Image-recognition models support uploading image files. If the model function is not correctly matched, you can find the model in the model list of the corresponding service provider, click the settings button after its name, and check the image option. Specific model information can be found at the corresponding service provider. Like embedding models, models that do not support vision do not need image functionality to be forcibly enabled; checking the image option will not have any effect. --- # Agent Instructions: 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: ``` GET https://docs.cherry-ai.com/docs/en-us/question-contact/questions.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.