cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Advocate II
Advocate II

PVA does not follow the flow / logic defined

Hi all,

I have a very comprehensive flow in PVA across several topics.

Each topic includes a defined flow with questions and conditions, each drives the flow to different directlion.

At the end of each flow, I'm sending the information through an SQL connector and writes to a table.

So far all works well...

Problem is, when I test the bot, it runs through each step according to the branch its in, and before reaching to the last step of opening the connector, it continues to the other branches and continue asking questions, even though the flow should not get there.

Only once it runs through all objects and collect all info, it gets to the last step of the topic and finishes.

Any idea why?

Please find a screenshot to highlight how it jumps between questions (logic should have been 1-2-3-5 as can be seen, but before it gets to 5, it moves to 4 from a reason I don't understand and then goes to 5).

The 2nd image is high view of a more complex flow, where the yellow line is the expected route to take. The red arrow is what PVA is doing once it finishes the expected route.

Hope I managed to explain my problem.

Any advice would be much appreciated.

Thanks,

 

PVA - Inconsistent.jpgPVA - Inconsistent.PNG

Thanks.

1 ACCEPTED SOLUTION

Accepted Solutions

Hello @HaimOz ,

 

Are you using a variable in step 5) that is defined in step 4)?

 

The Power Virtual Agent engine does not send a "Null" value to Power Automate, so if a variable is not defined, it jumps to the node which fills it in. In this case, I suspect step 4) is filling the value for a variable that is used in step 5).

 

Can you check that and let us know if that is the case?

 

Thanks

 

View solution in original post

2 REPLIES 2

Hello @HaimOz ,

 

Are you using a variable in step 5) that is defined in step 4)?

 

The Power Virtual Agent engine does not send a "Null" value to Power Automate, so if a variable is not defined, it jumps to the node which fills it in. In this case, I suspect step 4) is filling the value for a variable that is used in step 5).

 

Can you check that and let us know if that is the case?

 

Thanks

 

View solution in original post

Hi @CleberM ,

You are absolutely right!

I am sending variables to Power Automate (update SQL table) and include all variables within the topic, even the ones not being used (as they are under another branch).

In Power Automate, when using the PVA trigger to send info (first action), I specifically set the input (/variable from PVA) as 'mark the field optional'. To me it means I'm allowed not to send anything from PVA. The fact PVA does not send a "NULL" value, kinda contradict its purpose, doesn't it?

Are you aware of any plan to change it in the future?

Also, as a workaround, I generate a dummy variable and send it to any unused field, depends on the branch I'm in.  If there's a better way to work around the limitation, I'd love to hear it.

Thanks for your help!

Helpful resources

Announcements
Microsoft Ignite

Microsoft Ignite

Join digitally, March 2–4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!

New Super Users

Meet the Power Virtual Agents Community Super Users!

Congratulations to our Season 1 2021 Super User Crew!

PVA Commnity Blog

NEW Power Virtual Agents Community Blog

View articles posted by fellow community members on the Power Virtual Agents Community Blog!

Microsoft Ignite

Microsoft Power Platform: 2021 Release Wave 1 Plan

Power Platform release plan for the 2021 release wave 1 describes all new features releasing from April through September 2021.

Top Solution Authors
Users online (27,203)