Notifications
Announcements
When creating a flow, this error arises.
I was getting that error when my variable type saved by pva didn't match the variable type being sent back to power automate. So if I have a "choice" variable and power automate is expecting a string variable, it will give you that error.
As @ajpayne indicated, you likely have some sort of mismatched variable type and/or missing data being passed between PVA and Power Automate.
Power Automate can only accept, and can only return, text, number, and yes/no (boolean). If you update inputs/outputs in Power Automate after you've already added the flow in PVA that can also create problems as well. You can click on the "..." in the top -right corner of the Power Automate node within PVA and select "Refresh" to refresh the connection to the flow and ensure PVA understands what it needs to send to, and what it gets from, Power Automate (see below screenshot)
You can read more about this here:https://mattjimison.com/2023/06/23/updating-power-automate-flow-calls-for-legacy-power-virtual-agents-imported-into-the-unified-canvas/
Cheers,
Matt
Find this post helpful? Please mark it as the solution and/or provide kudos so that it will help others in the future.Cheers,Matt
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.
In our never-ending quest to improve we are simplifying the forum hierarchy…
We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Michael E. Gernaey 255 Super User 2025 Season 2
Romain The Low-Code... 205 Super User 2025 Season 2
S-Venkadesh 101 Moderator
