Virtual Agent topics are not catchying the associated NLU model after deploying to other instances

[Ivan Delchev]

Hi guys,

I am currently developing Virtual Agent topics and NLU model in one scoped application in our DEV environment. I am publishing the application to our company repository and then installing it in upper environments like TEST and PROD. The problem is that the topics are not catching the associated NLU model when the application is installed. Everything else is fine - the topics are there, the NLU model is there, but it is not associated with the topics. And in DEV everything is fine:

Do you have any ideas about why this isn't working?

Thank you!

[Tony Chatfield1]

Hi, what are the results of your debugging? Have you checked your logs for errors? Ensured all scope related functionality/ table and script access etc was captured and transferred between instances? Does your code reference specific sys_ids anywhere and if yes where these records sourced from the same instance via clone or XML import?

[darius_koohmare]

A suspicion I have is that it is removing the reference because technically the intent is not part of an active published model. When you move the NLU model to prod, did you ensure there was a trained model available? Then the references should be valid.

[Ivan Delchev]

Hi, the model was trained and everything was saved and published in DEV prior publishing the application and installing it in TEST environment. The problem is that I am not able to make any changes directly in TEST - I should develop everything in DEV then populate to upper instances..

[NaAs · Accepted solution]

try re-publish the NLU model.