Common client errors (4xx)
- Print
- PDF
Common client errors (4xx)
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Available in Classic and VPC
While using the CLOVA Studio service, you may encounter the following issues. Check the cause and solution for each issue and act accordingly.
HTTP status code | Code | Message | Causes | Solution |
---|---|---|---|---|
400 | 40000 | Bad request | Invalid request | Check the API specification to check the request syntax |
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 | Text too long | Request text too long | Reduce the length of the entered text so that it doesn't exceed the number of tokens the model can process, or lower the maximum tokens in the parameter and then 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 1 | Request where results can't be provided due to internal policy | - |
400 | 40006 | Unavailable output 2 | Request where results can't be provided due to internal policy | - |
400 | 40009 | Unsupported function | Requested unsupported features | Check whether the request syntax supports tuningType or Chat completions/Completions |
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 |
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 value |
401 | 40102 | Invalid access token | Invalid access token | Reissue access token with valid client ID and client secret value |
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 value |
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 |
406 | 40600 | Not Acceptable | Invalid media format | Check whether the media format is valid |
408 | 40800 | Request timeout | Request processing timeout | Retry the request |
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 |
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 (traffic overload): Due to limited computing resources on GPU infrastructure, even if the user uses the service within the set maximum usage, processing delays or failures may occur depending on infrastructure conditions and traffic | - |
Note
Configuring your system to reference HTTP status codes helps ensure reliable operation.
Was this article helpful?