Hi
The boolean comparison condition is failing an always follow the one path for true or false. The variable is set by the return value of by Call Action node; the same variable is used to compare.
The boolean value captured by the Ask Question node is working fine with condition checking. In the case mentioned above also tried by checking the variables on the watch for values.
Finally, fixed by returning an integer value instead of boolean type.
Please suggest what might be causing the issue.
Thanks,
Abison Mathew Jose
Hi Abison,
this a bug that is being fixed. The fix should roll out end of this week.
@abison007 we have a known issue with flow boolean return values causing the issue you're describing. We are fixing this and should be live in a couple of weeks.
There are some workarounds like you mentioned above, which is a temporary solution until the fix goes live.
I did solve the problem by returning 0 or 1 and compare against integer.
Below is a screenshot of the condition.
Additionally pasting the return value part of the flow as well.
Hi @abison007 ,
Can you take a picture of your condition, please?
I need to understand how can you use the Power Automate response to Power Virtual Agents and how can you build your condition.
Did you solve using 0 or 1 numbers inside the condition?