---
title: "Troubleshoot error messages"
slug: "clovaspeech-troubleshoot-error"
updated: 2026-09-17T09:33:50Z
published: 2026-09-17T09:33:50Z
canonical: "guide.ncloud-docs.com/clovaspeech-troubleshoot-error"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot error messages

Available in Classic and VPC

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

## "No more slot" error message

When I use Long sentence recognition>Live streaming recognition (gRPC), the "No more slot" error message is displayed.

#### Cause

This error may occur temporarily when the call volume is concentrated at that time. When the access error occurs intermittently in the streaming recognition service, this error may occur.

#### Solution

As this error message is displayed when the call volume is concentrated temporarily, try to call again after a certain time.

## "ERROR_INVALID_SECRET" error message

"ERROR_INVALID_SECRET" error message is displayed.

#### Cause

This error may occur when the Secret Key value was entered incorrectly.

#### Solution

- Check if the Secret Key is correct.
  - To check the Secret Key, see [Long sentence recognition builder > Check API call information](/docs/en/clovaspeech-builder-long#API%ED%98%B8%EC%B6%9C%EC%A0%95%EB%B3%B4%ED%99%95%EC%9D%B8).
- Check if the Invoke URL is correct.
  - If you drag and copy the Invoke URL, the value may be missing. Click the **[Copy]** button to copy the value.

## "RESOURCE_EXHAUSTED" error message

- "RESOURCE_EXHAUSTED:Too many channels, the max channel is: 15" error message is displayed.
- Even if it just maintains the single streaming connections, the "RESOURCE_EXHAUSTED" error occurs.
- "No more available resources for connecting gRPC" error message is displayed.

#### Cause

The number of simultaneous connections to gRPC is limited to 15 per domain. When the number of connections exceeds 15, this error may occur.

#### Solution

- Once the voice recognition ends, end the gRPC connections.
  - To end channels, use common development codes, such as channel.shutdown and channel.close. For detailed examples, see the content for live streaming recognition.
  - Maintain the channel connections in the unit of single streams where voice recognition requests continue.  

Example: in the case of live broadcasting, end the gRPC connections at the time the live broadcasting ends.
- It is recommended to apply the timeout logic depending on the transfer/receipt of voice recognition data.
  - If you continue to maintain the connections while there is no transfer/receipt, a problem occurs in obtaining gRPC channels.

## "ERROR_REQUEST_PARAMETER" error message

"ERROR_REQUEST_PARAMETER" error message is displayed. "Speaker detect is off" error message is displayed.

#### Cause

The diarization.enable value is entered incorrectly. diarization.enable is used as follows: `"diarization" : { "enable" : false }`

#### Solution

When you do not enter diarization.enable value, `true` is applied by default. When you set the speaker detect status to "Off", set the diarization.enable value to "false", then call. For more information, see [Long sentence recognition builder](https://api.ncloud-docs.com/docs/en/ai-application-service-clovaspeech-longsentence).

              Note

              

If you're still having trouble finding what you need, click on the feedback icon and send us your thoughts and requests. We'll use your feedback to improve this guide.