Failed to install flow error

(0) Share

Report

Posted on by BradonK

375

Hi all,

I'm having an issue with an app I have developed.

I have a production environment where the app has been imported. In the app is a flow that runs when a button is pressed.

When I run the app in the production environment I don't get an error. But when I share the app with someone and they click it, the following error occurs.

GenerateITPDocument.Run failed: {"error":{"code":"0x80048d06","message":"Failed to install the flow"}}

I saw another post about this but the solutions on it did not fix my issue.

https://powerusers.microsoft.com/t5/Building-Power-Apps/Failed-to-install-the-flow/td-p/2503171

According to the above post, it's an issue with the latest version of Power Apps. However, I cannot change this in the production environment, and the issue only occurs with the person the app is shared with. So not entirely sure it's Power Apps that is the issue.

Any help appreciated.

Categories:

Building Power Apps

I have the same question (0)

All responses (13)

Answers (1)

Sort by

Datanerd 103 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @BradonK ,

This is a common case scenario, to troubleshoot:
Check Flow Connections:
Verify that the flow uses connections that the person running the app has access to. If the flow uses connections that are specific to your account, the other person may need to create their own connections or update the flow to use their connections.
Flow Error Details:
Look into the flow's run history for more details on the error. In Power Automate, go to the flow, click on "Run History," and then check the details of the specific run that failed. This might provide more insights into the root cause.
Recreate the Flow Connection:
Try recreating the connection in the flow. Delete the existing connection in the flow and add it again, ensuring that the new connection belongs to the user who is experiencing the issue.
Export and Import the App:
Export the app from your environment and import it into a new environment. Share the new environment with the person facing the issue and see if the problem persists.
Check Flow Dependencies:
Ensure that the flow doesn't have dependencies on specific resources or configurations in your environment that might be missing in the other person's environment.
Please let me know if this helps.

Was this reply helpful? Yes No
BradonK 375 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Datanerd ,

I have tried the solutions posted in the post I linked originally.
This includes deleting the flow from the solution, importing the solution to prod.
Re-adding the flow back and importing the solution to prod again.

The flow does not have any error runs as it doesn't appear to run at all.

One thing to note, the flow uses two connections. SharePoint and Encodian.
I have an Encodian connection that uses an API key from my Encodian account.
I have added the user that is getting this error as a Run-Only User on the flow with the Encodian connection set to Use This Connection.

The error only occurs for the person I'm sharing the app with, not for me. But both are in the same environment, so I think all dependencies should be the same and available.

Was this reply helpful? Yes No
BradonK 375 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Datanerd,

Just seeing if there is any update on this. The issue is still occurring.

Was this reply helpful? Yes No
SurferDan0603 21 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @BradonK,

I had the same and was driving crazy!
I´m not sure if this error always has the same cause, but I was able to fix it by changing the permissions in my connection. I´ve added another user in my dev-environment and had to set a permission to my organisation in the test-environment.

I hope this helps you!

Was this reply helpful? Yes No
BradonK 375 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @SurferDan0603 ,

Could you let me know what you changed the permissions for? Are you talking about a connection reference?
I can't find any permissions that I can change for a connection reference. All my tables have their read and write perms set to 'Organization' in the security role for the user.

Thanks

Was this reply helpful? Yes No
SurferDan0603 21 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @BradonK ,

sure, you are able to select the connection in the menu on the left side. Here you can administrate the connections within the specific environment. If you click on your connection you can share it to other users.

So overall in my case: I had to share the connection in test-environment with my organization. After that they were able to proceed the flow in the app.

PS: Sorry, maybe was 'permission' not exactly the correct wording...

Was this reply helpful? Yes No
BradonK 375 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @SurferDan0603 ,

No worries, I found it.
I have shared the Encodian connection that the flow uses as I believe it is the issue.
I also have a SharePoint connection the flow uses but It is meant to use the runtime user's SharePoint so I don't think I should share it and have thus left it.
I'll get back to you on if this works.

Cheers!

Was this reply helpful? Yes No
blink182_joel 24 on at

Like
a
(1)

Report
Copy link

Link copied!

I had this issue yesterday. It turned out that in the app, which was using the flow, in the code, it was using the the name of the flow that had automatically been generated, when it was first created. For some reason it looked fine and worked fine in Dev, but when I moved to Production, it knew it wasn't right, so solution is to remove, readd the flow in the app, then ensure the name of the flow in the code actually reflects the name of the flow.

Was this reply helpful? Yes No
BradonK 375 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @blink182_joel ,

Thanks for the idea, but that doesn't seem to be the case for me. The flow is named correctly in the code so don't think that's the issue.

Was this reply helpful? Yes No
ngohw 95 on at

Like
a
(0)

Report
Copy link

Link copied!

I've been struggling with this issue for the past couple of weeks -- I've had it happen twice but both times the culprit was completely different.

The first time it happened to me was due to an environment variable I forgot to use inside a flow step.

The second time it happened, I never quite figured out why it happened, but judging from the error code 0x80048d06 it seemed Dataverse related. The only fix I found for this was to create a new flow and recreate the affected flow from scratch, adding it to my solution and hooking it back up to my app in Maker Studio.

It is extremely tedious and it's ridiculous that I even have to resort to this, but this seems to be the only way to fix it. Some flows in my solution weren't affected, but they don't have Dataverse steps... could be related, could be unrelated! Hope this helps.

Was this reply helpful? Yes No