Troubleshooting CLOVA Studio

Available in Classic and VPC

This document details problem situations that users may face while using CLOVA Studio, as well as their causes and resolutions. Click each problem situation to go to the related page.

Request processing successful (2xx)

Common problem situations users might encounter are as follows.

20000 OK
The API call was successful, and the response status code indicates 20000.

20400 No content
The API call was successful, and the response status code indicates 20400.

Common client error troubleshooting (4xx)

Common client error problem situations users might encounter are as follows.

40000 Bad request
The API call failed, and the response status code indicates 40000.

40001 Invalid parameter
The API call failed, and the response status code indicates 40001.

40003 Text too long
The API call failed, and the response status code indicates 40003.

40004 Text empty
The API call failed, and the response status code indicates 40004.

40005 (TBD)Unavailable output 1
The API call failed, and the response status code indicates 40005.

40006 (TBD)Unavailable output 2
The API call failed, and the response status code indicates 40006.

40009 (TBD)Unsupported function
The API call failed, and the response status code indicates 40009.

40080 model not found
The API call failed, and the response status code indicates 40080.

40082 model fade out
The API call failed, and the response status code indicates 40082.

40100 Unauthorized
The API call failed, and the response status code indicates 40100.

(TBD)40101 Invalid signature
The API call failed, and the response status code indicates 40101.

(TBD)40102 Invalid access token
The API call failed, and the response status code indicates 40102.

(TBD)40103 Access token expired
The API call failed, and the response status code indicates 40103.

(TBD)40104 Invalid key
The API call failed, and the response status code indicates 40104.

(TBD)40170 No subscription request history found. Please request a subscription to use
The API call failed, and the response status code indicates 40170.

(TBD)40300 Forbidden
The API call failed, and the response status code indicates 40300.

(TBD)40301 No ownership
The API call failed, and the response status code indicates 40301.

(TBD)40400 Not found
The API call failed, and the response status code indicates 40400.

(TBD)40600 Not Acceptable
The API call failed, and the response status code indicates 40600.

(TBD)40800 Request timeout
The API call failed, and the response status code indicates 40800.

(TBD)41500 MediaType error
The API call failed, and the response status code indicates 41500.

(TBD)41501 No multipart boundary Content-Type
The API call failed, and the response status code indicates 41501.

42900 Too many requests
The API call failed, and the response status code indicates 42900.

42901 Too many requests - rate exceeded
The API call failed, and the response status code indicates 42901.

42902 Too many requests - overloaded
The API call failed, and the response status code indicates 42902.

Client skill error troubleshooting (4xx)

Client skill error problem situations users might encounter are as follows.

40010 input_text_empty
The API call failed, and the response status code indicates 40010.

40020 missing_input_value
The API call failed, and the response status code indicates 40020.

40020 missing_input_value
The API call failed, and the response status code indicates 40020.

40030 invalid Action
The API call failed, and the response status code indicates 40030.

40040 invalid Action Input
The API call failed, and the response status code indicates 40040.

40050 internal parsing error
The API call failed, and the response status code indicates 40050.

40060 (TBD)Lora app id must have hyperclova url
The API call failed, and the response status code indicates 40060.

Common server error troubleshooting (5xx)

Common server error problem situations users might encounter are as follows.

50000 Internal server error
The API call failed, and the response status code indicates 50000.

50100 Not yet implemented
The API call failed, and the response status code indicates 50100.

50400 Gateway timeout
The API call failed, and the response status code indicates 50400.

Server skill error troubleshooting (5xx)

Server skill error problem situations users might encounter are as follows.

50010 no final answer
The API call failed, and the response status code indicates 50010.

60000 HyperCLOVA API Error url:{url}
The API call failed, and the response status code indicates 60000.

64000 {HyperCLOVA error message}
The API call failed, and the response status code indicates 64000.

64240 {HyperCLOVA error message}
The API call failed, and the response status code indicates 64240.

64290 {HyperCLOVA error message}
The API call failed, and the response status code indicates 64290.

65000 {HyperCLOVA error message}
The API call failed, and the response status code indicates 65000.

51010 There are no tools available for planning.
The API call failed, and the response status code indicates 51010.

51020 An unknown error occurred during planning. {reason}
The API call failed, and the response status code indicates 51020.

51030 Unable to plan for the given query. The reasons are as follows. {reason}
The API call failed, and the response status code indicates 51030.

Content to explore

NAVER Cloud Platform provides information in a variety of ways to help our customers. Here's a guide to useful content that you can utilize when using the CLOVA Studio service.

• NAVER Cloud Platform online training: Utilizing NAVER Cloud Platform API