cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
niknaks456
Regular Visitor

Cant re-add a flow to PVA after I have updated it

Hello all, not sure if this is a bug or 'm just doing silly.

 

I had a PVA working fine and then I added something more to a flow.  The PVA told me I needed to remove and read the flow to get the changes.  I removed and went to add the flow from the 'call an action option' option.  From here I can see my flow fine but when I click to add it back into my PVA it simply wont.  I can add other new flows just fine but not the one I updated.

 

I have tried different browsers, logging in and out.  If I recreate the same flow with a new name I can add the flow to my PVA but that's a real pain for ongoing development every time I need to change a flow.

 

Any clues on how to fix this.  Also is there a way to just update the flow in the PVA with an update button?

1 ACCEPTED SOLUTION

Accepted Solutions
MarKol
PVA
PVA

Hi,

 

 can you please try remove any spaces or other non-alphanumeric characters (underscores are OK) from the flow's inputs/outputs and try adding this flow again? 

 

There is a bug currently being fixed that makes PVA reject the flows with non-alphanumeric characters as valid. This workaround should make PVA accept this flow.

 

PS: the "Refresh" button for flows is on the roadmap and should be coming soon.

View solution in original post

9 REPLIES 9
renatoromao
Super User
Super User

Hi @niknaks456 ,

 

It's not normal this issue.

Can you take some pictures inside your Power Automate workflow?

Just to understand better your scenario, but depending on your situation, you can open a ticket to Microsoft.

 

---

Thanks!

Renato Romão

https://www.linkedin.com/in/renatoromao/


Did I answer your question? Mark my post as a solution!
Thanks!

Renato Romão,

Connect with me here 😉

Power Virtual Agents course (+2.300 students | PROMOTIONS) : English | Português
MarKol
PVA
PVA

Hi,

 

 can you please try remove any spaces or other non-alphanumeric characters (underscores are OK) from the flow's inputs/outputs and try adding this flow again? 

 

There is a bug currently being fixed that makes PVA reject the flows with non-alphanumeric characters as valid. This workaround should make PVA accept this flow.

 

PS: the "Refresh" button for flows is on the roadmap and should be coming soon.

View solution in original post

Whew! Couldn't figure out why my flows weren't getting added all day! Finally!!!

hmm, i think i have it sorted now via your help.

 

I removed numbers from the return values, so I had '365prinname' as the name of the return value and removed '365' which seems to have fixed it.  I also took out number in the name of the flow as well just in case.

I ran into this today--I have several virtual agent topics that call actions that return text strings. Today I created a new flow, but couldn't add it to a topic; I'd select Call action, then select the flow name, and nothing would happen. I took the numbers out of the title of the flow output, and then I could select the flow name and the flow would be added to the topic.

 

So "alphanumeric characters" doesn't quite fit. Letters work, underscores work. Numbers don't work.

Egbert
Frequent Visitor

Through a process of trial and error I think I found an underlying problem.

 

Any variable name returned by the "Return value(s) to Power Virtual Agents" must be no more than 10 characters long. I think removing whitespace just shortened the names below 10 chars.

Anything 11 or more means that when you attempt to add the action to a PVA topic, it will just ignore the attempt to add.

 

This one works:

Egbert_0-1602646000721.png

While this won't:

Screen Shot 2020-10-14 at 2.30.03 pm.png

Egbert
Frequent Visitor

turns out that the issue I experienced with variable names of length>10 only causes upset in one bot, and not another.

so, there's something else going on

Egbert
Frequent Visitor

Chrome and Edge both show the same stack trace when you try to select one of these unselectable actions:

 

Egbert_0-1603347885941.png

 

Hi @MarKol ,

Thanks for the answer. I removed all spaces and special characters and finally I could use my Flow.

Regards,

Fernando

Helpful resources

Announcements
March Update

Welcome to the User Group Private Preview

Check out new user group experience and if you are a leader please create your group

MBAS on Demand

Microsoft Business Applications Summit sessions

On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks

MBAS Attendee Badge

Claim Your Badge & Digital Swag!

Check out how to claim yours today!

Top Solution Authors
Top Kudoed Authors
Users online (35,774)