Unable to Publish NLU model in UAT

Yasmin
Kilo Guru

When migrating VA and NLU updates into UAT environment via updateset we are able to train the model, but it does not allow to publish the model. With the migration, there were some new utterances included, so we need to train and publish, but it only allows to train and the publish button is not enabled. What could be causing this? Thanks.

find_real_file.png

1 ACCEPTED SOLUTION

Thanks brianbakker. We tried eliminating the 0% progress record from the ML_solution.list but it still wouldn't allow to publish after training it.

Somehow this was related to another NLU issue that I reported on this thread "VA topic not mapped to NLU Intent" where the name of one the topics was the same name as the intent. Though this wasn't an issue before, it now seems to not let NLU mapped objects to work properly. Once I changed the name of the intent to be different from the VA topic name, I was able to train and publish the the model successfully.

Link to related article that solved this issue: VA topic not mapped to NLU Intent

View solution in original post

6 REPLIES 6

Thanks brianbakker. We tried eliminating the 0% progress record from the ML_solution.list but it still wouldn't allow to publish after training it.

Somehow this was related to another NLU issue that I reported on this thread "VA topic not mapped to NLU Intent" where the name of one the topics was the same name as the intent. Though this wasn't an issue before, it now seems to not let NLU mapped objects to work properly. Once I changed the name of the intent to be different from the VA topic name, I was able to train and publish the the model successfully.

Link to related article that solved this issue: VA topic not mapped to NLU Intent

Brian Bakker
ServiceNow Employee
ServiceNow Employee

I am pleased that you managed to resolve the issue by changing the name of the intent to be different to the topic name.

Indeed this is strange behaviour and this could be a new defect, so if you need Technical Support to investigate further and to engage the Dev team to confirm whether this new behaviour is expected or not, please raise a new case via the ServiceNow Support web site and we will gladly investigate this further.

Best regards,

Brian