Skip to main content
Known Participant
April 24, 2025
4. Future Consideration

Additional Log Information

Related products:Agent StudioEmployee Experience InsightsKnowledge Studio
  • April 24, 2025
  • 3 replies
  • 41 views

I would like to know if the Moveworks platoform provides a way to view conversational history in the logs. There may be some issues with the triggering of plugins that are launching when they should not be. It would be very helpful if we could view the conversation the user had with the bot so we could identify the user input that triggered the plugin call. 

When viewing the analytics page, it does not provide any information about plugins. Is this something that is available? It would be very helpful to review the entire convesation history to see how users are interacting with the bot, what type of questions they are asking, and what conversations are triggering plugins. 

    3 replies

    Ajay Merchia
    Community Manager
    April 26, 2025

    Hey ​@justinrous, we are working on adding a plugin filter log, but the utterance of the user will be redacted for security & privacy reasons.

    We’ll likely add some admin controls so you can unmask this eventually, but in the mean time, if you’re looking to debug plugin triggering, can you share a few instances you’re unable to troubleshoot?

    Known Participant
    April 28, 2025

    Hi ​@Ajay Merchia , yes being able to view the utterances would be very beneficial and the conversation history. For example, we have a plugin that should trigger to clear the Teams cache if an employee chats with the bot with an issue related to MS Teams. However, this plugin seems to be triggering much more frequently than intended, even after creating comprehensive triggering for the plugin.

    It would be helpful to view the utterances that is triggering this plugin. They are not available in the logs. Also, it seems that interaction history doesn’t show interactions that called a plugin, so I cannot view the utterance in the interacetion history. 

     

     

    Ajay Merchia
    Community Manager
    May 5, 2025

    Got it – thank you for this feedback. It makes sense that you should be able to validate the quality of your trigger. We’ll keep this in mind :)