cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
New Member

Flow can't be found after importing a chatbot solution

I have a chatbot that calls a few flows. One of these flows has an Adobe Sign connection to send a document for signature. When I import the chatbot into a new environment, I see an error in PVA that says "We ran into a problem importing some flows. They may not work correctly and could block publishing. Add flow connections and turn them on in Power Apps Solutions

Sure enough, when I open that Flow, I see that the Adobe Sign connection hasn't come along with it. I can recreate the connection, but when I test the flow, I get the error: "Flow '112a1d5e-bf9c-14a9-4dfd-1aa517af9d83' cannot be installed."

 

Later, when trying to edit or run the flow, I sometimes see this error: "The XRM workflow entity could not be found."

 

If I run the bot in PVA, most of the flows work fine, but when the bot calls the flow with the Adobe Sign connection, i get the error: "Sorry, the bot can't talk for a while. It's something the bot's owner needs to address. Error code: 2012. Conversation ID: DGjDy7LbxevECBnwu5KvpA-f. Time (UTC): 11/24/2020 11:20:29 PM."

1 ACCEPTED SOLUTION

Accepted Solutions

@tonyd3Sharp , there is a known limitation that the PVA trigger flows cannot be executed directly in the Power Automate portal, we have a future work item to address it.  However, this should work when the flow is called by the bot in PVA's test bot.

 

Could you confirm after fixing the connection and turning the flow on, running the flow via PVA bot still throws the error?

View solution in original post

8 REPLIES 8

Hi @tonyd3Sharp , thank you for reporting this issue, could you confirm if the flow is turned on?

New Member

Yes, it is turned on. It was initially turned off after import, but I turned it back on.

 

Thank you @tonyd3Sharp for the response and being patient.  We are looking into it.

@tonyd3Sharp , there is a known limitation that the PVA trigger flows cannot be executed directly in the Power Automate portal, we have a future work item to address it.  However, this should work when the flow is called by the bot in PVA's test bot.

 

Could you confirm after fixing the connection and turning the flow on, running the flow via PVA bot still throws the error?

View solution in original post

New Member

Yes, I have confirmed it now works in PVA. Not sure at what point it started working, as I think I had reverted to testing in Power Automate. Thanks for all the help, everybody!

 

Regular Visitor

I farted

Regular Visitor

Plz reply if u want me to give u some info

Regular Visitor

I will give u info if u reply hi to this message

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 Automate Super Users!

Many congratulations to the Season 1 2021 Flownaut Crew!

New Badges

New Solution Badges!

Check out our new profile badges recognizing authored solutions!

MPA Community Blog

Power Automate Community Blog

Check out the community blog page where you can find valuable learning material from community and product team members!

Top Solution Authors
Top Kudoed Authors
Users online (44,272)