Announcements
I was working with my bot, and connecting to Flow to pull a row from Excel. Everything appeared to work and I can see no issue in trace process, but the bot errors out instead of proceeding to the next step. I am sure I will have many errors, is there a way to see the exceptions?
https://powerva.microsoft.com/canvas?cci_bot_id=8a04ab3f-3dfc-4cc1-8280-8557a52bb4a4&cci_tenant_id=38564255-3626-447b-ae4b-2644ab10162f
The error is happening in Flow so I would suggest if you get an error in Flow that you set an indicator in an an output variable returned to Virtual Agent. In Virtual Agent you can test the output value to see if an error has occurred and if so output a friendly response to the the bot user
hth
Joe
That was my first thought as well, but the flow looks completely successful, even with the correct JSON in the response:
Sorry you confused me now - Is the error in the flow?
The flow has never failed. It logs complete success and payload as expected. Even the action step in my bot is successful, but the bot still ends with error.
The bot says: Sorry, something went wrong. I am not able to help you at the moment, please check back later.
So I have no clue what might be the issue and how/where to troubleshoot it, especially since the flow is successful.
Sounds like a timeout waiting for Flow to complete. Check it works if you call another Flow - maybe a dummy with a fixed response.
The flow runs in < 3 seconds. It is a simple flow to get a row from an excel stored in sharepoint.
On my first bot in the same env, I was able to follow along and get the greeting tutorial to work.
I'll mess with it more later, but back to my original question, where are the logs? If it is timing out, that should be trapped and surfaced somewhere?
It is a SaaS platform so in depth errors not usually available. Goto analytics and exports sessions and you can see conversation and what session where escalated or not resolved.
You should also able to query the Bot entities in the CDS environment but I have not looked at these in depth yet
By pulling down the bot snapshot, I was able to see the error with JSON. Specifically, the JSON Schema I had defined had one more field than the JSON Payload I built, so it was erroring out at the bot side to parse the JSON. Ideally Power Automate would have recognized the fundamental issue here, but it shows as a pass and completes successfully.
In this case, and I am guessing many others, the error surfaces in the Snapshot JSON you can download!
Thanks!
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Valantis 177
Romain The Low-Code... 130 Super User 2026 Season 1
chiaraalina 45 Super User 2026 Season 1