> For the complete documentation index, see [llms.txt](https://en.help.firstline.cc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://en.help.firstline.cc/feature/chatbot/scenario/troubleshooting.md).

# Troubleshooting

## The linked script is not responding

When your script fails to respond properly after being associated with the specified pipeline, this may be due to some common issues in the script design or settings. The main causes and their corresponding solutions are as follows:

1. **The script is not enabled**If the script is disabled, even if it is successfully associated with the pipeline, it will not perform any actions when triggered, and the flow will end immediately.
2. **The sub-script starts with "Event"**If a sub-script starts with "Event", it must wait until it receives a user's message or meets other specified event conditions before it can continue. If these events do not occur during the expected interaction, the script will not automatically proceed to the next step.

***

## The script does not advance through the workflow as expected

If your script does not proceed according to the expected flow, you can check the following points:

### Using a \* wildcard for the first event at the same level

If the first event or decision node at the same level uses the wildcard "\*", any customer message will match immediately and proceed to the first flow branch. This may cause subsequent keyword checks to stop working, and you need to adjust the left and right positions of the decision nodes.

<figure><img src="https://842546780-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MNRu7dk70ei7JV9HlW9%2Fuploads%2FH4swhtYwkWxocngFeQQu%2Fimage.png?alt=media&#x26;token=3490508c-a509-461d-a606-b2f0b5251af4" alt=""><figcaption></figcaption></figure>

### Different types of nodes placed at the same level

When different types of nodes are placed at the same level, such as "Event" and "Condition" being judged on the same level, subsequent nodes of different types at that level will not be executed.

<figure><img src="https://842546780-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MNRu7dk70ei7JV9HlW9%2Fuploads%2FjW3623ZDLJWNnli13683%2Fimage.png?alt=media&#x26;token=2e97f419-a0ed-412f-b0f2-b951d9d668cf" alt=""><figcaption></figcaption></figure>

### **Is there exception handling**

Some customers may enter text manually instead of using the options provided in the interface. To handle this situation, you can add the keyword "\*" after a node at the same level for fuzzy matching.

<figure><img src="https://842546780-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MNRu7dk70ei7JV9HlW9%2Fuploads%2FcW1542iJcRdJJvCynTn9%2Fimage.png?alt=media&#x26;token=d2e27c05-6bc2-4f90-845d-f7eb4d787554" alt=""><figcaption></figcaption></figure>

### Missing conditions in the judgment rules

If you use keywords to determine the flow direction, it is recommended to check whether any keywords are missing. For example, if you set the keyword to "A" but the customer does not send "B" as expected, you may need to check whether more keywords should be added, or use another method to handle unknown cases.

<figure><img src="https://842546780-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MNRu7dk70ei7JV9HlW9%2Fuploads%2FxhAbpGuekMBpNa7pkHhu%2Fimage.png?alt=media&#x26;token=4724e3b8-0619-432e-9b6b-577239fee34c" alt=""><figcaption></figcaption></figure>

### The script exceeds the 100-node limit

To avoid designing overly long flows, which can result in poor user experience and make management difficult, a single script has a node limit. When your design needs to exceed the limit, it is recommended that you use third-party integrations (such as APIs) or redesign and split it into sub-scripts, modules, and other components to create a simpler and more user-friendly flow. This way, both you and your customers can get the information you need more quickly.

***

## How to import a script designed in another environment

If you want to import a bot script designed in another FIRST LIN system environment, please go to the specific script and switch to "Edit Mode". At the top of the interface toolbar, you will see a note icon. After clicking it, you can select a JSON file designed in another environment. Once selected, click the "Import" button, and the system will automatically import the script design you chose. This feature allows you to easily import script content from other systems into our system, improving work efficiency and convenience.

<figure><img src="https://842546780-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MNRu7dk70ei7JV9HlW9%2Fuploads%2FGIvFQFupdHm0jQBRv433%2Fimage.png?alt=media&#x26;token=29c1cf3e-653c-46fb-b7ad-0c91229632e1" alt=""><figcaption></figcaption></figure>

***

## How to verify a test script

For simple debugging, you can follow these steps:

1. **Simplify the flow scope:** When you suspect there is a problem with a node or flow, simplify the flow scope to the smallest possible range. For example, create a test script with only 3 to 4 nodes instead of too many. This helps verify whether it meets the required support while reducing complexity.
2. **Test step by step:** Add nodes step by step and test them, observing the behavior at each stage. This helps determine exactly where the problem occurs and quickly identify possible causes.
3. **Record inputs and outputs:** When testing, record the input and output of each node in detail. For example, you can intersperse "Note" nodes, which can help you trace the flow and find the possible source of errors.

***

## Common reminder messages

### The selected scenario id is invalid

When you see the error message "The selected scenario id is invalid", it means that in the script flow, you may have used node functions such as "Go to another script", but the sub-script linked to that node has been deleted, preventing it from connecting to the corresponding script correctly.

To solve this problem, you need to check the script flow and ensure that all nodes and sub-scripts are correctly linked and exist. If you confirm that a certain sub-script has been deleted, you need to update the corresponding node to connect to a valid sub-script or delete the invalid node.

### The selected text conv event id is invalid.

When you see the error message "The selected text conv event id is invalid.", it means that in the script flow, you may have used node functions such as "Flow Tracking", but the event linked to that node has been deleted, preventing it from being connected correctly.

To solve this problem, you need to check the script flow and ensure that all nodes and events exist correctly. If you confirm that an event has been deleted, you need to update the corresponding node to connect to a valid event or delete the invalid node.