Before you use TQL to analyze your bot's sessions make sure that:
Conversations you had in Try Out in Studio do not show up in the Log Data Source and are not queryable; you need real data to use TQL. If your bot meets the prerequisites, you can skip this section. Otherwise, we walk you through the steps to get you to the point where you can start using TQL.
TQL needs data to work with. Once your solution has been published, users can interact with it. You can read more about publishing your bot in this section.
Follow these steps to publish the Longberry Baristas solution. If you've already published this solution you can continue with the next section.
You might see a warning Publish to 'Default env' stopped with warnings appear. This is nothing to worry about; the warning is shown when you publish your solution for the first time or when you have made certain global changes. To proceed, just check the checkbox 'Perform full application deployment on try again' and click the 'Try again' button.
If you check the Publish view in Studio and do not see a URL or a publish history, you have not published your bot and you will need to do so.
If you're chatting with your bot in a browser directly via the publish URL it will look something like this:
The final step assures that the session ends immediately. This in turn allows the session to become immediately available to TQL queries. If you forgot to end the session in this way, the session will still become available to TQL queries after a default timeout period of ten minutes.
Was this page helpful?