Answered

Flow can't be found after importing a chatbot solution

(0) Share

Report

Posted on by tonyd8132

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."

Categories:

General topics

All responses (12)

Answers (1)

Sort by

CU22081450-0 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @tonyd3Sharp ,

To solve the Adobe Sign issue, you can try Log out of Adobe Sign from the browser, Log out of the Power Automate, Close all browsers, Start a new session, Login to Power Automate again and set the connection. It should work (Don't login to Adobe Sign at first).

If the issue persists, please, take a picture and send it here.
tonyd8132 20 on at

Like
a
(0)

Report
Copy link

Link copied!

No luck. I also noticed that the connection did not appear in "My Connections", so I tried removing it entirely and creating it there, but that didn't work either.
CU22081450-0 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

@tonyd3Sharp ,

Did you already try to create a new workflow and create the same action inside this new workflow?

Because maybe your issue is related to the Adobe Sign connection and not to your workflow.
tonyd8132 20 on at

Like
a
(0)

Report
Copy link

Link copied!

Yes, I am able to create other workflows that use Adobe Sign actions, however, if I create one from within PVA, it fails with the same error, just giving a different GUID.
CU22081450-0 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

@tonyd3Sharp
Thanks for reporting this issue!

I will send to the Microsoft team, and besides, you can create a ticket inside the PVA support: https://powervirtualagents.microsoft.com/en-us/support
tonyd8132 20 on at

Like
a
(0)

Report
Copy link

Link copied!

I appreciate it!
micchow Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

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

Like
a
(0)

Report
Copy link

Link copied!

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

Like
a
(1)

Report
Copy link

Link copied!

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

micchow Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

@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?