Debug a Virtual Agent topic

  • Release version: Yokohama
  • Updated January 30, 2025
  • 2 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Debug a Virtual Agent topic

    This guide helps ServiceNow customers investigate and resolve unexpected behaviors in custom Virtual Agent topics, topic blocks, and controls. It emphasizes best practices for safely debugging topics without impacting live users and provides tools and methods for effective testing and issue identification.

    Show full answer Show less

    Debugging Best Practices

    • Duplicate Before Editing: Always duplicate a live topic before making changes. This preserves the original as a backup and reference, allowing quick restoration if needed. Remember to deactivate the original topic before publishing your duplicate.
    • Test Conversations During Development: Use the Test button in Virtual Agent Designer to preview conversations as they appear in Service Portal. Since third-party messaging platforms may display conversations differently, also test topics in those external environments where you plan to deploy.

    Debugging Tools in the Test Chat Window

    The test chat window contains four tabs to assist with debugging and refining topics:

    • Analyze test phrases
    • Variables
    • Context
    • Logs

    These tabs help identify processing messages, errors, and warnings during conversation testing.

    Identifying and Resolving Warnings and Errors

    • Control Warnings: Controls missing required information display a red incomplete badge showing the number of issues. Clicking the badge reveals detailed issues to fix.
    • Topic-Level Warnings: A badge on the canvas indicates the total number of issues in the entire topic.
    • Validation Issues: When a topic preview fails to run, a Validation Issues tab shows the total errors and provides hyperlinks to problematic nodes, helping you quickly navigate and correct errors. You must resolve all issues before publishing the topic.

    Common Issues and Resolutions

    • Missing Module Designer: Ensure the user has the virtualagentadmin role and the Virtual Agent plugin is activated.
    • Cannot Edit Topic: Confirm the user is in the same application scope as the topic.
    • Cannot Preview Topic: Verify all required node fields are completed and browser pop-ups are allowed for the instance.
    • Chat Widget Stuck on "Connecting...": Check that topics exist on the instance and are in the Active state.

    Reviewing Conversation Flows and Interaction Records

    Each Virtual Agent conversation automatically generates an interaction record in the Interactions [interactions] table. This record logs the full conversation transcript between the requester, Virtual Agent, and any live agent transfers. Reviewing these records helps analyze real interactions for troubleshooting and improvement.

    Troubleshooting Natural Language Understanding (NLU) Issues

    If an intent is not being selected as expected, investigate NLU prediction errors and understand how Virtual Agent’s topic discovery logic returns and prioritizes intents. Properly diagnosing NLU issues ensures your Virtual Agent accurately interprets user inputs.

    Investigate and resolve unexpected behavior in your custom Virtual Agent topics, topic blocks, and controls.

    For information about topic discovery issues, see LLM topic discovery in Virtual Agent and Resolve Natural Language Understanding (NLU) topic discovery issues.

    Duplicate a live topic before debugging and changing it

    Duplicate a topic rather than update a live topic. The unmodified original topic can serve as both a reference and a backup, and retaining the original enables you to restore the topic quickly. Remember to deactivate the original topic before publishing the duplicate.

    Debug a topic while testing your conversations

    As you create or update a topic in Virtual Agent Designer, use the Test button in the topic header bar to preview the conversation. The chat test window shows the conversation as it appears within Service Portal. Elements in your conversation might appear differently in third-party messaging applications. Test your conversations in any third-party applications where you intend to deploy Virtual Agent.

    The test chat window displays four tabs that provide detailed information for debugging and refining your topic: Analyze test phrases, Variables, Context, and Logs. For details on these tabs, see Testing NLU/Keyword topics. The following example shows the processing messages and errors logged during testing.

    Conversation preview logs shown in the topic preview window.

    Watch for warnings on controls within your topic

    Figure 1. Warnings on a topic node in the Flow tab
    Number of warnings shown in red on the canvas and on the individual controls. For the Text User Input control, Node Name and Prompt are mandatory

    Controls that are missing necessary information show a red incomplete badge in the upper left corner of the control. The badge shows a number indicating the number of issues in that control. Select this badge to see a list of the issues in the control.

    Another warning badge appears in the upper left corner of the canvas to indicate the number of issues within the entire topic.

    Check for errors when a topic preview does not run

    Figure 2. Topic preview errors on the canvas
    The topic validator window giving a preview of errors on the canvas.

    Additional information appears in a Validation Issues tab on the sidebar of the Virtual Agent Designer canvas when an error prevents the topic from running. The total number of Issues are listed, along with details and a hyperlink for each node. Select a hyperlink to go to the node, and use the information provided to correct any errors in your conversation. You can close the tab without correcting the issues, but until the issues are corrected, the Validation Issues tab appears when you select Publish. The Validation Issues tab closes if you select Publish after correcting all issues.

    Common Virtual Agent issues

    Issue Possible resolution
    Cannot see module designer under conversational interfaces
    • User might not have the virtual_agent_admin role.
    • Virtual Agent plugin might not be activated.
    Cannot edit a topic Logged-in user must be in the same application scope as the topic.
    Cannot preview topic
    • Make sure that all required fields are filled in on the node properties.
    • Ensure that your browser is configured to permit pop-ups from your instance.
    chat widget stuck at Connecting... One or more of your topics might be missing. Check the to ensure that topics are present on the instance and in the Active state.

    Review topics that run in a conversation flow

    Each Virtual Agent (VA) conversation in an instance automatically generates an interaction record in the Interactions [interactions] table, which logs the conversation between a requester and virtual and live agent. You can review the transcript of the conversation between the requester and virtual agent, including live agent transfers (if using Agent Chat). For details, see Virtual Agent interaction records.