NLU to LLM migration log

The Topic Migration Execution Items [topic_migration_execution_item.list] table includes data when migrating Natural Language Understanding (NLU) topics to large language model (LLM) topics such as the migration status, migration issues, and migrated or published topic information.

You can access this topic migration data either by searching for topic_migration_execution_item.list in the Navigation pane or downloading the .CSV file version of the table. After you've migrated topics, the downloadable .CSV file is accessible through the Review migration log option in the topic migration workflow's Migrate topics step.

그림 1. Example of the Review migration log option

The Topic Migration Execution Items [topic_migration_execution_item.list] table defaults to include the following columns:

• Description
• Issues
• LLM Topic
• Migration Execution
  주:

  The Migration Execution column includes the unique ID that is generated for each migration batch. For example, when 10 topics are migrated at the same time, the table contains 10 topic rows with each row containing the same migration execution value.
• Migration status
• NLU Topic
• Status
• Type

그림 2. Example of the Topic Migration Execution Items table data

Generic issues may occur during the topic migration process. The following table includes specific, common issues that you may encounter in the Issues column and whether the issue blocks the topic from being published.

표 1. Issues column details

Issues column value	Types of issues	Can the topic be published?
Some topic properties couldn’t be generated. To publish, manually review and edit the following nodes: [list of node names]	Node-level issues: These issues are validation error messages that can include missing fields such as name, description, and so on.	No. The issue must be corrected before the topic can be published.
Some topic properties couldn’t be generated because the topic used a script. To publish, manually review and edit the following nodes: [list of node names]	Script-level issues: These issues occur whenever an NLU input node has a script or data pill in the Prompt field.	Yes. Topics with this issue can be published because Collect [Node Name] populates in the Detailed description field, but the value of the Detailed description field value should be revised and improved.
Some topic properties couldn't be generated. Edit them before publishing the topic.	Topic-level issues: These issues are validation errors at the topic level such as a missing description, keywords, or any other required field.	No. The issue must be corrected before the topic can be published.
The topic description couldn’t be generated. Edit the description field on the Publish page or from the topic properties page in Virtual Agent Designer before publishing.	LLM-generated description issues: These issues occur whenever LLM is unable to generate a valid topic description.	Yes. Topics with this issue can be published because the [Topic name] populates the Topic description field, but the Topic description field value should be revised and improved.
The topic description couldn’t be generated because the mapped intent wasn’t found. Edit the description field on the Publish page or from the topic properties page in Virtual Agent Designer before publishing.	LLM-generated description issues related to NLU intent complications: These issues occur whenever an NLU model and intent is mapped to a topic but is missing from the sys_nlu_model or sys_nlu_intent table or if these values are incorrectly mapped to the topic.	Yes. Topics with this issue can be published because the [Topic name] populates the Topic description field, but the Topic description field value should be revised and improved.
The topic description couldn’t be generated because both the intent and keywords are missing. Edit the description field on the Publish page or from the topic properties page in Virtual Agent Designer before publishing.	LLM-generated description issues related to NLU intent complications: These issues occur whenever an NLU model's intent and keywords aren’t mapped to the topic.	Yes. Topics with this issue can be published because the [Topic name] populates the Topic description field, but the Topic description field value should be revised and improved.
The migration tool couldn’t convert one or more dynamic topic block nodes from this topic. The topic blocks used inside the dynamic topic blocks must be manually migrated. The following nodes use these dynamic topic blocks: [list of node names]	Dynamic topic block issues: These issues occur whenever there’s a node that has a dynamic topic block that wasn’t migrated.	Yes. Topics with this issue can be published because the topic block names use a script for dynamic topic blocks and continue to operate as expected, using the NLU topic block. If you encounter this issue, select these topic blocks for migration from the Select topics step and update the topic block names in the script.
The migration tool couldn’t convert one or more switch topic scripts from this topic. The topics used inside the switch topic script need to be manually migrated. The following nodes use these switch topic scripts: [list of node names]	Switch topic script issues: These issues occur whenever a node has a switch topic function that wasn’t migrated.	Yes. Topics with this issue can be published because the topic script continues to use the NLU topic until migration. If you encounter this issue, select these topics for migration from the Select topics step.
This topic couldn't be migrated. Contact ServiceNow support for assistance.	Process failure issues: These issues occur whenever there's an error during a particular migration process.	No. The issue must be corrected by a ServiceNow employee before the topic can be published.
This topic couldn't be migrated because the transformation of NLU nodes to LLM nodes failed. Contact ServiceNow support for assistance.	Process failure issues: These issues occur whenever there's an error during the transformation of NLU nodes to LLM nodes.	No. The issue must be corrected by a ServiceNow employee before the topic can be published.
This topic couldn't be migrated because the publish payload failed to generate. Contact ServiceNow support for assistance.	Process failure issues: These issues occur whenever there's an error during a particular migration process.	No. The issue must be corrected by a ServiceNow employee before the topic can be published.
This topic can’t be published until a topic description is added.	Process failure issues: These issues occur whenever there's an error during a particular migration process.	No. The issue must be corrected before the topic can be published. Edit the description field on the Publish step or from the topic properties page in an Virtual Agent Designer topic before publishing.