클라이언트 스킬 오류 문제(4xx)
- Print
- PDF
클라이언트 스킬 오류 문제(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 | Cause | Solution |
---|---|---|---|---|
400 | 40010 | input_text_empty | Requested query, thought, action, actionInput, and observe parameters as empty | Request after filling in the blanks |
400 | 40020 | missing_input_value | Some input values are missing | Request after filling in missing values |
400 | 40030 | invalid Action | Entered an undefined action | Check the API specification and use the defined requests_get or requests_post to enter |
400 | 40040 | invalid Action Input | Entered an invalid actionInput | Check the API specification to enter a defined actionInput |
400 | 40050 | internal parsing error | Internal parsing error | Check request syntax by checking the API specification |
400 | 40060 | Lora app id must have hyperclova url | It occurs when the model is not found | Request again after checking server status |
400 | 40099 | {HyperCLOVA error message} | Errors related to HyperCLOVA input (text too long, etc.) | Reduce the length of the entered text so that it doesn't exceed the number of tokens the model can process, or use the API Spec extension to reduce the API response and then request |
429 | 42901 | {HyperCLOVA error message} | HyperCLOVA too many requests error: Too many requests to the model | Control the request or retry to avoid exceeding maximum usage |
Note
Configuring your system to reference HTTP status codes helps ensure reliable operation.
Was this article helpful?