---
title: "Troubleshoot common issues"
slug: "clovachatbot-troubleshoot-common"
updated: 2026-09-17T09:33:47Z
published: 2026-09-17T09:33:47Z
canonical: "guide.ncloud-docs.com/clovachatbot-troubleshoot-common"
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 common issues

Available in Classic and VPC

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

## Interpreter feature unavailable in chatbot

When LINE English interpreter is invited to a chat connected to a chatbot on LINE, the interpreter immediately leaves the chatroom.

#### Cause

Because two bots (chatbots) cannot exist in one chat room, interpretation cannot be used during chatbot conversations. If the chatbot’s reply inputs to another bot, and that bot’s response inputs back, it can cause an infinite loop.

#### Solution

As explained in the cause section, it is a normal operation and it does not need any action.

## Build issues

The build does not complete.

#### Cause

Training time varies by data volume, but with fewer than 100 conversation datasets, training completes within 5 to 10 minutes. If only one conversation is registered and training is performed, the dataset may be too small and cause training failure.

#### Solution

Input at least 10 conversation datasets and run tests. No charges occur if the build fails.

## Welcome message not displayed

Although a welcome message was registered, it does not appear during testing.

#### Cause

If the conversation model is not built, the welcome message may not display.

#### Solution

- After registering the welcome message, confirm that you completed quick conversation build, model build, or applied changed settings.
- During manual testing, check if you clicked the **[Start with welcome]** button.

## Localhost usage not allowed in chatbot responses

When trying to use a URL in chatbot replies, localhost addresses cannot be used.

#### Causes and solutions

Localhost addresses are not allowed.

## API call text result error

When calling the API using Python code for chatbot Custom integration, results may not appear correctly.

#### Cause

You must complete service deployment in the build history menu for API calls to respond correctly.

#### Solution

Confirm that you did not complete only beta deployment.

## Regular expression question error

A regular expression set in a conversation question does not work as expected.

#### Cause

The regular expression question length is limited to 500 characters.

#### Solution

Enter regular expression questions within 500 characters.

## NAVER TalkTalk integration error

An error occurs during NAVER TalkTalk integration.

#### Cause

- Integration information was entered incorrectly.
- The registered webhook URL in TalkTalk partner center does not match the domain API URL in use.

#### Solution

- Check the integration information.
- Confirm that the registered webhook URL matches the API URL of the domain in use.

## Chatbot icon change

You cannot change the chatbot icon image.

#### Cause

Changing the icon in the builder is not supported by specification.

#### Solution

As explained in the cause section, it is a normal operation and it does not need any action.

## Data local backup

You want to back up data locally from the console.

#### Causes and solutions

Local backup functionality is not provided. To create a new chatbot using existing data, use the domain copy function or download and save conversations, user variables, entities, etc.

              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.