Virtual Agent Topic linked to NLU model cannot be saved or Publish Issue After the instance upgrade to Pairs, the topic that linked to the NLU (natural language understanding) model cannot be save or published.ReleaseQuebecCauseThere are records linked to affected topic in sys_cb_topic_language, sys_cs_topic_language table in different scopes comparing to sys_cb_topic and sys_cs_topic records on the instance.ResolutionMake the correction to keep all the related records to the same topic in the same scope: Create a record in the same scope and remove the one not in the same scope to solve the issue by the steps below: Example below was the affected topic record in sys_cb_topic_language was in global scope, but the VA topic scope is in 'ITSM Virtual Agent Conversations': (IT Service Management)1. Make sure that you are in global scope, open the affected record: a. Navigation: sys_cb_topic_language.listb. search the topic name and find the affected record 2. Make a duplicated tap, and change the application scope to use 'ITSM Virtual Agent Conversations' 3. Back to the screen on step 1, click 'insert and stay' on the context menu to create the record, make sure that this record is in 'ITSM Virtual Agent Conversations' application, then click update. 4. Switch the scope to the global scope and delete the existing invalid record who is in global since the correct record was created in step 3.Follow the same steps 1 - 4 to create a new sys_cs_topic_language record in 'ITSM Virtual Agent Conversations' scope and delete the wrong scope recordTo make sure that all four records for 'Check Ticket Status' on sys_cs_topic_language, sys_cb_topic_language, sys_cs_topic and sys_cb_topic should in the same scope 'ITSM Virtual Agent Conversations' and the issue should be solved.