Troubleshoot common issues

Available in Classic and VPC

The following describes issues that may occur while using CLOVA Studio and how to resolve them.

Errors during a surge in concurrent requests

An error occurs when multiple users send API requests simultaneously.

Cause

CLOVA Studio has limits on the number of API requests and tokens that you can use within a given time frame. For more details on the policy, see the CLOVA Studio usage control policy.

Solution

• Check the QPM value in advance, and make requests within the maximum value.
• Implement and add a separate API call control feature (rate limit).
• Separately add a certain time delay feature (time sleep) between requests.
• If the HTTP 429 code is returned with an error message, process an exception and request again after a certain time delay.
• For instructions on managing to avoid exceeding the maximum usage, see Maximum usage management.

Return of errors

Errors were returned during the API call.

Cause

The causes and resolutions vary depending on the errors. There are various factors, such as API request format, authentication information, and exceeding the rate limit.

Solution

The cause and resolution should be checked based on the returned errors. For detailed explanations of each errors, see CLOVA Studio troubleshooting in the CLOVA Studio API guide.

Unable to edit or delete the service app

After applying for or registering a service app, it cannot be edited or deleted.

Cause

Features for editing or deletion of the service app are not provided.

Solution

If the service app needs to be edited, perform the work anew and then apply for the service app.
If only the prompt and parameters need to be edited in a service app for the same model and API, it is acceptable to change the API call information of the already registered service app. However, if the service information to which the service app is to be applied changes, a new application must be submitted.

Tasks to be requested are not displayed when applying for a service app

After selecting a model in the service app application information, nothing appears in the list of Tasks to be requested.

Cause

The service app reviewer must save the Playground and tuning tasks and generate a shareable URL so that the task contents can be directly reviewed. The list of Tasks to be requested is displayed only if they are created using the selected model and saved.
#### Solution

• Create a task using the selected model and save it.
• Check whether a task has been created in the playground and sharing is enabled. For instructions on creating a task sharing URL, refer to Task sharing.