Virtual Agent NLU doesn't work

[Junyu]

Dear all,

I am testing NLU for Virtual Agent in San-Deigo release version. I have created the NLU model and published it:

Question:

1. But when I tested it on the portal, it doesn't work:

2. And when I tried to publish another small talk topic, the errors occurred:

3. I don't know where to set the "confidence threshold" of NLU in the San-Diego release version, is it necessary for me to install "NLU Workbench plugins"?

Can anyone help me answer these three answers? Thanks a lot.

[Victor Chen]

First, "hi" is likely too short for the NLU to recognize depending on your intents and utterance setup. It may also conflict with an existing out-of-box Setup Topics NLU model. 

You're also not allowed to bind the same intent to multiple topics. That looks like what you've done but it's difficult to tell by the screenshots alone. 

Finally, the confidence threshold in San Diego can be set at the model level: Model > Manage your model Content > Settings. 

[Junyu]

Hi Chen,

1. What does "Topic is bound to more than one model group for English, Chinese: small talk_test, test. Please remove duplicative bindings, republish, and re-bind the appropriate model group." mean and what should I do next?

2. Here's my model content. Is "Needs utterances" a warning? How to remove this?

3. How can I remove this blue warning in Virtual Agent Topic Properties?

 

[Junyu]

Hi @Victor Chen ,

Can you give me some follow-up advice?

[nilimadesai · Accepted solution]

Hi Junyu,

For the 'small talk greeting' topic intent disabled issue, I would try to retrain and republish the model. Based on your screenshots, does seem like the topic is enabled. 

For the 'topic bound to more than one model group' error seems like there is some data corruption that may have ended up occurring in sys_cs_topic_language and/or sys_cb_topic_language tables. Could you please review the NLU Models and Intents associated to VA topics in these tables and if you find duplicates, remove such associations from Designer and reassociate the correct ones. Without access to the instance it is hard to know for sure. 

In case you are not sure how to troubleshoot, it maybe best to open a NOW Support case so a support engineer can investigate further. 

Thanks,

Nilima