❓Troubleshooting
The linked script does not respond
When your script fails to respond after being associated with the specified flow, this may be due to some common issues in the script's design or settings. Below are the main causes and their corresponding solutions:
Script not enabled: If the script is disabled, even if it is successfully associated with the flow, it will not perform any actions when triggered, causing the process to terminate immediately.
Subscript begins with “event”: If a subscript begins with an “event,” that script requires receiving a user message or meeting other specified event conditions before it can proceed. If those events do not occur during the expected interaction, the script will not automatically execute the next step.
Script does not proceed as designed
If your script does not progress as expected, you can check the following points:
Wildcard * used in the first event at the same level
If, in the same level of event evaluation, the first event or decision node uses the wildcard '*' , any customer message will immediately match and go to the first flow branch. This may cause subsequent keyword evaluations to fail; you need to adjust the positions of the decision nodes.
Different node types placed at the same level
When different types of nodes are placed at the same level—for example, “event” and “condition” evaluated on the same level—subsequent nodes of different types at that same level will not be executed.
Is there exception handling
Some customers may type text themselves instead of using the options provided by the interface. To handle this situation, you can add the keyword '*' at the same level of nodes to perform fuzzy matching processing.
Missing judgment conditions
If you determine flow direction by keywords, it is recommended to check for missing keywords. For example, if you set the keyword to “A,” but customers do not send “B” as you expected, you may need to add more keywords or use other decision methods to handle unknown situations.
Script exceeds the 100-node limit
To avoid designing overly long flows that lead to poor user experience and difficult management, a single script has a node limit. If your design requires exceeding the limit, it is recommended to use third-party integrations (such as APIs) or redesign and split into subscripts, modules, etc., to create a more simplified and user-friendly flow. This allows you and your customers to obtain the needed information more quickly.
How to import scripts designed in other environments
If you want to import a bot script designed in another FIRST LIN system environment, go to the specific script and switch to “Edit Mode.” On the interface toolbar above, you will see a notebook icon. After clicking that icon, you can choose the JSON file designed in the other environment. After selecting it, please click the “Import” button and the system will automatically import the script design you selected. This feature allows you to easily import script content from other systems into ours, improving work efficiency and convenience.
How to verify and test scripts
When doing basic debugging, you can follow these steps:
Narrow the flow scope: When you suspect a node or flow has problems, simplify the flow to the possible minimal scope. For example, create a test script that contains only 3–4 nodes instead of too many nodes. This helps verify whether the needed support is met while reducing complexity.
Test step by step: Add nodes step by step and test, observing the behavior at each step. This helps determine the specific location of the problem and quickly find possible causes.
Log inputs and outputs: When testing, record the input and output of each node in detail—for example, you can insert “note” nodes. This can help you track the flow and find possible sources 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 nodes like “go to another script,” but the subscript associated with that node has been deleted, causing an invalid connection to the corresponding script.
To resolve this issue, you need to check the script flow and ensure all nodes and subscripts are correctly associated and exist. If you confirm a subscript has been deleted, update the corresponding node to link to a valid subscript or remove 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 nodes like “flow tracking,” but the event associated with that node has been deleted, causing the link to fail.
To resolve this issue, you need to check the script flow and ensure all nodes and events exist correctly. If you confirm an event has been deleted, update the corresponding node to link to a valid event or remove the invalid node.
Last updated