Frequently Asked Questions

Common error codes

  • 4xx (Client error status codes): Generally indicates request syntax errors, authentication or authorization failures, or other issues that prevent completing the request.

  • 5xx (Server error status codes): Generally indicates server-side errors, such as server crashes or request processing timeouts.

Error code
Possible causes
Solutions

401

Authentication failed: model not supported or server account suspended, etc.

Contact or check the corresponding service provider account status

403

Request operation not permitted

Follow the error message returned in the conversation orConsoleerror message prompts to take corresponding actions

404

Requested resource not found

Check the request path, etc.

422

Request format is correct, but semantic error

These errors can be parsed by the server but cannot be processed. Common with JSON semantic errors (e.g., null values; a value required to be a string but written as a number or boolean, etc.).

429

Request rate limit reached

Request rate (TPM or RPM) has reached the limit — wait a bit before retrying

500

Internal server error, cannot complete the request

If it persists, contact the upstream service provider

501

Server does not support the requested functionality, cannot complete the request

502

A server acting as a gateway or proxy received an invalid response from the upstream server while attempting to fulfill the request

503

The server is temporarily unable to handle the client's request due to overload or maintenance. The duration of the delay may be included in the server's Retry-After header

504

A server acting as a gateway or proxy did not receive a timely response from the upstream server


How to view console errors

  • Click the Cherry Studio client window and press the shortcut keys Ctrl + Shift + I(Mac:Command + Option + I)

  • The current active window must be the Cherry Studio client window to open the console;

  • You need to open the console first, then click test or start a conversation request to collect request information.

  • In the popped-up console window click Network → Click to view the last item marked in red at position ② × of completions(When encountering errors with conversations, translations, model connectivity checks, etc.) or generations(When encountering errors with painting/drawing) → ClickResponseto view the full returned content (the area marked ④ in the image).

If you can't determine the cause of the error, please screenshot this interface and send it to the official community group for help.

This inspection method can obtain error information not only during conversations but also when testing models, adding knowledge bases, drawing, etc. In all cases you must open the debug window first and then perform the request operation to capture request information.

The Name (item ② above) field will vary 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 shown directly, check whether the formula has delimiters

Delimiter usage

Inline formula

  • Use single dollar signs: $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\sum_{i=1}^n x_i

  • Formula rendering errors / garbled text often occur when the formula contains Chinese characters. Try switching the formula engine to KaTeX.


Unable to create knowledge base / failed to get embedding dimension

  1. Model status unavailable

Confirm whether the provider supports the model or whether the provider's model service status is normal.

2. A non-embedding model was used


Model cannot recognize images / cannot upload or select images

First confirm whether the model supports vision. Popular models in Cherry Studio are categorized; models that support vision have a small eye icon after their name.

Vision-capable models will support image file uploads. If the model functionality is not correctly matched, find the model in the provider's model list, click the settings button after its name, and check the image option.

Detailed model information can be found from the corresponding provider. Like embedding models, models that do not support vision do not need to have image functionality forcibly enabled; checking the image option has no effect.

Last updated

Was this helpful?