Debug Skills

During testing of Skills within the bot, the developer/administrator can leverage the Debug Utility that helps understand any issues that may occur during skill execution. Debug log contains the series of events inside the Bot. The information about various conversation items of the skill, like the context of the operation, rulesets, and local/global attribute values can be viewed as part of the debug logs. The debug logs for the current skill being tested are viewed by clicking the  icon in the test widget. You can debug a skill once Build and Publish is completed so that the virtual agent can execute the current skill to be debugged. 

The information on the list of conversations to the bot from multiple channels can be viewed from the Conversation History workspace while Debug skills helps you analyze any issues that may occur during skill execution.

<include icons for the bot and user in the sentence below>

All the data that comes from the bot is shown with the bot icon next to it and the data from the user is represented with the user icon. 

1. The existing debug log can be downloaded by clicking on the Download () icon. A text file will be downloaded which includes all of the debug data of current skill that is being tested.  
2. Use the Clear () icon to clear the debug history.

The Debug page displays all the events when a skill is being executed such as the start and end of a conversation flow, success or failure of a message, response sent, message received, and so on. The following image shows few events.

You can click the icon next to the required event to see the issues in detail as shown below.

The context of the Web Service Operation will be shown by clicking on the event "Operation Executed". This is useful when you want to know the Web service response and request data that is going to the web service from the virtual agent. This helps during the debug of the issues when the virtual agent needs to talk to external applications to perform skill fulfillment.

The context of the ruleset can be seen from RuleSet Evaluated event.