Export Creator Studio logs

Thank you for submitting your Product Idea. We understand this is not currently supported, we appreciate your feedback and will consider it in the future as we continue to build and improve our product. Please keep up to date with our latest release notes here.

Thanks for suggesting this feedback to our team @bwineke! As a quick followup, does your team use any log processing tools to parse this data today? Would love to understand your workflow better as we plan our investments for logs in 2024

This would be very useful. When building API connectors, sending information from Creator studio to Power Automate for example, there’s no way of checking what Creator Studio is sending to our HTTP listener in Power Automate until the HTTP listener receives the HTTP message. A use case may be passing user responses into slots, sending the slots via API to Power Automate, then populating an excel sheet or list of all responses for a given Event or Path.

For my workflow, if Power Automate never receives an HTTP message containing slot information for example, there’s no way to check which part of our API is set up incorrectly. This means I may end up having to delete the API and trying again from scratch. Luckily my team has documented the specific information to set up an API to Power Automate, but it took quite a bit of trial and error to eventually get the HTTP listener to receive the API commands.

Furthermore, even with a working Event/Path → API handoff, our bot will say “response was not submitted successfully” even though our Power Automate HTTP listener logs the bot interactions properly. It would be helpful to see the logs of every API handoff to understand what is being sent

Hi @sarthak - Currently we are accessing certain logs through ServiceNow as it is the middle layer for many of our use cases. The SN logs don’t give the full picture though on the bot side so additional details in the Creator Studio logs would be helpful. Adding @ckothha for additional input

There’s a LOT of data inside these logs – it can be very bloated and exporting the data isn’t considered a best practice from a security perspective. We’ve been making upgrades to exploring logs & troubleshooting (e.g. with our new Compound Action tester). Can you share more on why this is important to you.