During a test conversation in the Copilot Studio Test console, a maker notices that a condition node is taking the wrong branch. They suspect a variable has an incorrect value. What Test console feature helps them diagnose this without adding extra 'send message' nodes to display variable values?

The Copilot Studio Test console includes a real-time variable inspection capability. As the conversation progresses through nodes, the Variable watch panel shows the current values of all topic variables, global variables, and system variables that are in scope. This updates as each node executes, allowing makers to see exactly what value a variable holds at the moment a condition is evaluated. This feature eliminates the need for 'print statement debugging' (adding temporary message nodes to display values), a common but cumbersome workaround. The verbose logging approach that writes variable values to the conversation transcript is wrong because, while some logging integrations exist, the Test console doesn't have a verbose logging toggle that surfaces variable values in the transcript text; the variable panel is the correct tool. The CSV export approach is wrong because conversation transcripts can be reviewed, but they don't capture variable state snapshots at each node execution. The temporary 'Send message' node approach is wrong because it works but is the manual, invasive workaround the question explicitly asks to avoid; it also requires remembering to remove the debug node before production deployment. Exam debugging tip: the Test console variable panel provides live debugging for variable state. Combined with the topic navigation tracker, which shows which node is active, this gives makers all the information needed to diagnose most logic issues.