The Bot Logs window can display the log of the conversation that occurred in the Preview window or the log of any conversation that occurred in a supported channel. This makes it a useful tool in a few ways.

First, if you're encountering unexpected behavior, always check the Bot Logs window. Errors and failures are displayed in red, so you'll know at a glance if and where they occurred.

Second, because a log provides a more technical view of the underlying process flow that occurred during the conversation, it can deepen your understanding of how that processing works and support research. For example, you can use the log to identify the patterns or intents that were matched in the conversation.

Here's a visual overview of the Bot Logs window:

  • 1 = Use the User ID input box to specify the log you want to view.
  • 2 = Click (Refresh) to display or refresh the log.
  • 3 = Click the circle beside a logged event to display its timestamp.

Errors and failures are displayed in red, so you can spot them quickly.

Debug during bot development

To display the log for the conversation that occurred in the Preview window

  1. With the Dialogs page displayed, click Preview in the upper-right corner.
  2. In the upper-right corner of the Preview window, click Bot Logs. This toggles the display to show the Bot Logs window.

    For ease of use during bot development, by default, the user ID for the consumer in the conversation in the Preview window is entered in the User Id input box, and the associated logs are automatically displayed.

To aid in debugging, you can use the printDebugMessage scripting function in the code areas of an interaction to print messages – for example, the consumer's most recent message – to the Bot Logs window. For more on this function, see here.

Events glossary

Max limit on daisy chaining of interactions: 10

This error is:

BREAKING THE INTERACTION FLOW. Reached max limit on daisy chaining of interactions: 10

This error occurs when you have linked together 10 or more, consecutive Statement and/or Integration interactions within a single dialog. In other words, within those interactions, there are no Question interactions that stop the flow to ask for user input.

When the limit of 10 is reached, the interaction flow is stopped.

The limit of 10 is designed to prevent infinite loops and other potential error conditions.

Iteration count exceeded 5

This error is:

Breaking the interaction flow because iteration count exceeded 5

This error occurs when you have linked together 5 or more, consecutive Statement and/or Integration interactions across multiple dialogs. In other words, within those interactions, there are no Question interactions that stop the flow to ask for user input.

When the limit of 5 is reached, the interaction flow is stopped.

The limit of 5 is designed to prevent infinite loops and other potential error conditions.