Common client error troubleshooting (4xx)

Prev Next

Available in Classic and VPC

You might run into the following problems when using CLOVA Studio. Find out causes and possible solutions.

HTTP status code Code Message Causes Solution
400 40000 Bad request Invalid request Check the API specification to check the request syntax.
400 40000 Each user message can contain only one image 2 or more images are included in a turn. Edit to include one image per turn.
400 40001 Invalid parameter Invalid request parameter Adjust values to fit the supported range of a parameter or correct errors in the API request format.
400 40003 Context length exceeded Request too long Adjust the length of the input text or the number of images it contains so that it does not exceed the number of tokens that the model can process, or lower the maximum tokens in the parameter and then make the request.
400 40003 Image limit exceeded Maximum number of images per request exceeded. Edit to 5 images or less per request.
400 40004 Text empty Requested with empty text Fill in the empty content in the request body and then request.
400 40005 Unavailable output Request for which results cannot be provided -
400 40009 Unsupported function Requested unsupported features Check whether the request syntax supports tuningType or Chat completions/Completions.
400 40009 Unsupported function Unsupported tool request Select a tool that can process the request, or check whether the tool supports the request.
400 40009 Unsupported input format The model cannot process the requested input type. Change to a model that can process the requested input type, or edit the request.
400 40055 Invalid response format schema Response schema of unsupported format Change to a response schema in a supported format.
400 40060 Unsupported image format Unsupported image format included Change to BMP, PNG, JPG, JPEG, or WEBP image format.
400 40061 File size error Unsupported image size Change to an image size between 0 bytes and 20 MB.
400 40063 Invalid image size Image length exceeded. Request an image with the longer side measuring 2240 px or less and the shorter side measuring 4 px or more.
400 40063 Invalid image ratio Unsupported image ratio Change the image to a width-to-height ratio of 1:5 or 5:1 or less.
400 40063 Invalid image file Unprocessable image Try again after checking that the image file is normal.
400 40063 Invalid image url URL where image cannot be found Try again after checking that the URL can retrieve images normally.
400 40063 Image download failed Model failed to download image. Try again later.
400 40063 Image processing error Model failed to process image. Try again later.
400 40080 Model not found Model not found Request after checking the model name.
400 40082 Model fade out Model deprecation Change to a supported model to request.
400 40083 Model no resource No resources assigned to the model Check whether you have unsubscribed or terminated your contract.
400 40084 Unsupported API for model The request was sent to a model that is not supported by the API. Change the model to one that is supported by the API, or change to an API that supports the model, and then request again.
401 40100 Unauthorized Authentication failed Check the permissions of the task's creator and requester.
401 40101 Invalid signature Invalid request signature Reissue access token with valid client ID and client secret values.
401 40102 Invalid access token Invalid access token Reissue access token with valid client ID and client secret values.
401 40103 Access token expired Access token expiration Verify and reissue access token.
401 40104 Invalid key Invalid authentication key Reissue access token with valid client ID and client secret values.
401 40170 No subscription request history found. Please request a subscription to use CLOVA Studio subscription history can't be found. Check whether the CLOVA Studio service is subscribed in the NAVER Cloud Platform console.
403 40300 Forbidden Server operation denied Check permissions for requested features.
403 40301 No ownership No ownership Check permissions for requested features.
404 40400 Not found Requested resource not found Check whether the request syntax is valid.
404 40400 File not found Requested resource not found in the Object Storage bucket. Check whether the request syntax (file path) is valid.
406 40600 Not Acceptable Invalid media format Check whether the media format is valid.
408 40800 Request timeout Request processing timeout Retry the request.
408 40800 Image I/O timeout Model image download timeout Control the request or try again to avoid exceeding the maximum usage limit.
413 41300 Request body size exceeded Request body size limit exceeded Edit to 50 MB or less and request again.
415 41500 MediaType error Unsupported media format Check whether the media format is valid.
415 41501 No multipart boundary Content-Type Request that requires multipart use but doesn't fit the format Request by changing it to the format you need for multipart use.
424 42400 Processing Failed Problems occurred with some items while processing the request Check the request format and try again.
429 42900 Too many requests Too many requests To avoid exceeding the maximum usage set according to the pre-announced Usage control policy, check the relevant information in the response header at the time of request to control it within the maximum usage range or retry it using exponential backoff, etc.
429 42901 Too many requests - rate exceeded Too many requests (exceeding maximum usage) To avoid exceeding the maximum usage set according to the pre-announced Usage control policy, check the relevant information in the response header at the time of request to control it within the maximum usage range or retry it using exponential backoff, etc.
429 42902 Too many requests - overloaded Too many requests (excessive traffic) : Due to limited GPU infrastructure-based computing resources, even if the user uses the service within the maximum usage limit, processing delays or failures may occur depending on the infrastructure status and traffic.
429 42903 Too many requests - image queue Too many image requests (processing delay) Try again later.
Note

Configuring your system to reference HTTP status codes helps ensure reliable operation.