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.
400
Request body format error, etc.
Check the error content returned by the conversation or the console</a to view the error message and follow the prompt.
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 orconsoleerror 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)
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.
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.) orgenerations(when errors occur in drawing) → clickResponseto 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 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.
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
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$$∑i=1nxi
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
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.
Last updated
Was this helpful?