[Issue] "Flow.Run failed: Connection not configured for this service."

[RemiChambard2]

Hi,

I've built a Canvas application which calls a Power Automate flow from a button. The flow is using the "Power Apps v2" Trigger.

Both my Canvas application and Flow are deployed via a managed solution.

I've given the "Organisation Read" permission on the "Process" table in Dataverse for each user of the application.

Everything was working fine until this morning. Users could trigger the flow without any issue before. But since this morning, all users (except me) can't trigger the flow with the following error message : "[Flow].Run failed: Connection not configured for this service."

I've tried adding a user as "System administrator" on the Dataverse environment without any success.

Do you know about any specific curent issue on the topic?

Thanks for your help

[RemiChambard2]

Opening the app in Power Apps Studio, I can see that the Power Automate flow I call when I click on the button appears as "Not connected" in the list of Datasources. As if, the application has lost the "connection" with the flow.

After some testing, I can reproduce the exact same issue if I have an application that calls a Power Automate flow that doesn't exist in the environment.

Very very strange...

Still investigating...

[RemiChambard2]

One more thing : in the target environment, from Power Apps Studio, removing the connection to the Power Automate flow and adding it back again "solve" the issue. However, doing so, creates an unmanaged layer.

Removing the flow and adding it back again in the Dev environment before exporting the solution (in managed mode) to the target environment has no effect. The issue is still present.

Still investigating...

[skydivertak]

We had the same problem today. (We also had the problem 4 months ago). In both cases, we had to : comment out references to the Run(), remove the connection, re-add the connection, restore the code and save. We opened a ticket with Microsoft. We shouldn't have to do this with Production apps. I speculate that it might have something to do with licensing, as we also had some random licensing issues with an unrelated app at the same time.

BTW, we have the flow owned/connected with a system admin account.

[skydivertak]

I also noticed that they released a new version of Dataverse on February 25th (Saturday). Perhaps this, and previous updates have triggered the issue. Released versions of Microsoft Dataverse - Release Notes | Microsoft Docs

[RemiChambard2]

Thanks @skydivertak . I also saw the exact some report on the community forum last week (Flows not being triggered by PowerApp "Connection ... - Power Platform Community (microsoft.com)). It kind of "reassure" me. I strongly believe it's a MS issue. And I also agree with you that in any case, we shouldn't have to do that (update the production app).

I continue my investigation and will let know on that thread.

[CAC-93]

Ran into the exact same problem. While not a perfect solution creating the unmanaged layer in the target environment fixed the issue and is good enough for now. Thanks for the hint. Will be monitoring this to see if Microsoft will address this issue.

[CAC-93]

I think I may have found a solution to this issue, if anyone is still watching this. Want to put it out there to see if this actually helps and other people can apply it.

Go to the canvas application and view the solution layer.

The workflows triggered by power apps should be connected to the app, so you would expect to see them in the "connectionreferences" section in the unmanaged solution layer in my DEV environment.

Thing is there was no reference, so when you publish the managed solution it must not bring any indicator with it that the canvas app should be connected to flows with the PowerApps (V2) trigger. 

My goal: Get the connectionreferences to show the PowerApps (V2) triggered flows

This was actually pretty simple, I clicked "Add Required Objects"

....then the connectionreferences showed the workflows:

I tried reuploading to my TEST environment and it seems to work (NOTE! It also takes a minute or two for the app to fully register the update, so if it doesn't work you have to give it sometime before concluding that it actually doesn't work).

I have tried to troubleshoot this issue 1000 different ways so I am not sure if this is the actual solution, but if you can get the connection references to include your flows triggered by PowerApps, it might work. I don't know, but it seemed to for my team.

[BabaBaba]

Hi All

@CAC-93 On this thread and some others, people are talking about creating an unmanaged layer in the target environment (UAT in my case) on top of a managed layer.

First of all I can't see any option to create an unmanaged layer on top of a managed layer...

Your on your second solution (connection reference, Add required object), I checked that and found all connections already available.

I am using Power Apps Canvas App and connect to SQL server via Flow. Users cannot trigger the flow from the UAT Environment where the app/solution was brought in as Managed solution.

Microsoft support, after a long time thinking, asked me to put the AD group for users in the "Run As User" and specify the Connection on the same window. This also doesn't work.

Any ideas?

[CAC-93]

Monitor the user in your UAT environment and check if the flow installs correctly.

I believe there are multiple reasons for this "Connection Not Configured for this Service" issue, but one solution we have found is that a user requires "Read" access to the "process" entity in your UAT environment (something that is easy to see in the monitor because it will literally tell you that the flow install failed and then it will explain the user lacks something like "prvReadProcess"....or something like that (sorry I don't have that screenshot)"

Look at the user's security roles and give them Read access