Failed to install the flow

[get-spoash]

Hi there,

We have a solution which we are importing as a managed solution into the default environment.

We have 6 flows within the powerapp all triggered within the app, 4 are working fine but 2 are giving us the error below. They are all using the same connection reference.

The flow run only permissions are set to use the service account (account used for doing the import and all connections).

DegreePlanner-SendaswordDocument.Run failed: {"error":{"code":"0x80048d0b","message":"Failed to install the flow"}}

Any feedback would be appreciated.

[GlennBullion]

Same error here. Tried the solutions above, in terms of removing the flow, readding, re-exporting (all of which is ridiculous and time consuming). Same results.

[ngohw]

managed to fix it, ymmv!

1. flows were turned off in imported solution inside TEST environment -- turning them on provided a clearer error message
2. error message was linked directly to sharepoint step, i had forgotten to replace one of the properties with an environment variable i set up
3. fixed this in the DEV environment, removed connections from the app inside maker studio and added them back in, then redeployed to TEST environment
4. turned on flows without issue
5. didn't work immediately but gave it some time (~30 mins) and seemed to work no issues

it's also worth checking that the related security role(s) for the app has org-wide access to 'Process' under admin centre (aka.ms/ppac) and that you've shared the app directly with the group/users assigned to this security role

this seems like an extension of the existing power apps bug of 'Connection not configured for this service' that they still haven't fixed!

[AndreaPerolo]

Thank you ngohw for integrating my solution.

[pAAMckelvey]

@get-spoash, we tried your steps to resolve our issue and it did not work for us.  Still getting the error ...Run failed: {"error":{"code":"0x80048d0b","message":"Failed to install the flow"}}

[thecypher]

One thing that I have encountered with flows that I have imported from another environment was that. If you do not use the pipeline feature and export/import your solution as zip you can get an overlap with your flows installed in the previous environment. My flows apparently pointed to the old environment. So I deleted the solution from the test environment and then the flows in the dev env started working. It seemed as if the test env flows were overlapping the imported flows. Unfortunately I have no clue since I can't see under the hood of PA. Definitely worth testing it out. 

[pAAMckelvey]

Thank you @thecypher for your feedback.  We do use the Azure Dev Ops pipelines to promote our solutions from one environment to the next and have done so successfully for some time now.  This method is way easier than using the zip file method and manually exporting and importing solutions.  We make sure there are environment variables for everything like SharePoint site names and SharePoint list names, any text variables needed get an environment variable so that the solutions in each environment have their own resources and do not rely on anything from the original solution in our Dev environment. 

[ngohw]

This might be of interest if it's feasible within your environments:

Overview of pipelines in Power Platform - Power Platform | Microsoft Learn

While it is in preview I've only had positive experiences with it and you can also set up Power Automate flows in the background that sends emails to developers when their deployments have either succeeded or failed.

I've used Azure Dev Ops pipelines in the past for Power Platform projects and they're not as intuitive as Power Platform pipelines.

[pAAMckelvey]

Thanks for the link @ngohw .   For some reason these pipelines are not available in our environments yet.    I agree, the Azure Dev Ops Pipelines can be a bit tricky to setup but they have been pretty reliable.  I did build some instructions for our teams to use to get started quicker and have found I can copy pipelines and then update them to accommodate a new app so I don't have to start from scratch.

[EmerickJ161]

We had this same error.  We had an unmanaged layer and didn't realize it.  The unmanaged layer was removed and then, after redeploying, the app/flow worked perfectly.

[Digital_Admin]

We had every step you guys mentioned above! still not working.. my problem is only we three users so far. the only common thing between these users are in the same group but still the other users which are also in the same group and they work normally!

one of the three users i put his account as individual in flow permissions. the error message has changed to (connection not configured for this service) but the user has basic user permission in Dataverse and has organization read on flow process the same as other users! 

any suggestions! it is really urgent