Debugger

Find and Fix Errors Quickly and Easily

Parloa’s Debugger is designed to track transactions, logging every request to, and response from, the platform, along with every dialog node traversed.

Debugging Releases

Debugging releases are strictly for internal use. When accessed on multiple devices, all dialogs are linked to a single user, making this release unfit for client projects. To test on different devices, refer to the section on releasing.

Ensure debugging releases are not used for client projects to avoid data inconsistency.

The latest 15 transactions are displayed, with older ones being omitted for clarity.

Conversational Elements

Conversational elements mainly correspond to specific blocks from previous conversations. These elements feature eye symbols on the right side, selecting which navigates and zooms onto the respective block in the Graph, a visual representation of the dialog flow.

Flags for Error Handling

Flags are used within the Debugger to indicate errors or warnings. A flagged conversational element provides detailed insights into the nature of the error when selected. For example, an error in a Service block might be due to an incorrectly configured URL. Addressing warnings early on is recommended to prevent any unexpected dialog behavior.

It's advisable to address these warnings to prevent unexpected behavior.

Managing User Variables

Initially, the user variables section may display 'empty...' until variables receive assigned values through the use of storage or service blocks. Once a value is stored or modified, the associated block will be highlighted, providing a visual cue of the change.

For instance, if the variable 'roomName' is set to 'wolverine', the corresponding storage block 'saveRoom' will reflect this in the debugger.

Understanding Internal Variables

• currentNodeID – Indicates the current node and the subsequent node in the execution, with green marking the next node and red marking the current node.

• originNodeID – Represents the block where the current dialog request initiated.

• sessionCount – Counts the dialogs since the skill's first launch.

• requestCount – Counts all dialog requests since the skill's first launch.

• Prompts – Lists the recent prompts and reprompts from the last response of the dialog.

• accountIsLinked – States true if the user using the skill has it linked with a specific account; otherwise, the value is false.

• isNewConversation – The value of this variable equals true if the current request of the dialog is the beginning of the dialog or the start of the conversation. The variable states false if the current request is not the start of a conversation.

Platform-Specific Particularities

Each platform supported by Parloa has unique Debugger attributes, offering tailored debugging experiences. Invocation names should be distinct across platforms to avoid any overlap or confusion.

For phone-based interactions, if the caller ID is hidden, the variable will denote this with 'anonymous', ensuring privacy is maintained in the Debugger logs.

Caller History Insights

In the Debugger, you can access a history of the last 10 caller numbers or caller IDs associated with a particular release. Each caller entry provides a detailed breakdown of transactions and conversational elements from the last 30 days:

• Transactions – The last 15 transactions are displayed, as per the existing documentation.

• Conversational Elements – Up to the last 50 conversational elements are listed, providing a comprehensive view of the dialog flow.

If a caller conceals their number, the 'Caller ID' variable will commence with 'anonymous', enabling the viewing of anonymized calls in the Debugger logs.