Flow().RUN Error - Connection not configured for this service

[ricchiuto]

I have an app that invokes multiple flows. The app and flows exist in a solution and there are two environments (DEV & PROD). Everything works as expected in DEV, but when I import the solution into PROD, there are two users who get an error when completing the action(s) that invoke these flows.

It works with the service account used to create the solution, it works for two of the users, but for these other two particular users, they see this error consistently. I've tried to update/upgrade, delete/re-add the solution. All of the permissions are identical to the DEV environment.

Any thoughts on what to try?

[Pstork1]

Two things to check.

1) Make sure that all the flows are using Connection References and not just Connections. If they were created outside the solution and added later they will be using Connections.

2) Double check that you've set the Run Only user settings on the solution so user's use the connection from the connection reference and not one supplied by the user.

[JasonWS]

Are those other two members part of the environment? I've run into similar issues when just the app itself is shared with people without them being members of the environment.

[ricchiuto]

@Pstork1 thanks for your reply. Can you elaborate a little on the second point? 

[Pstork1 · Accepted solution]

In the details of each flow in the solution there will be an entry entitled Run Only users.  Click Edit

A panel will open on the right side showing what connection the users who run the flow will use. By default it will be provided by Run-Only user. Use the dropdown to change that to use a specific connection.

[KC]

Hi Pstork1, What version of the Flow details will show the Run Only users option? My instance does not have this.

Thank you!

[KC]

Never mind, found out the Run users only option only shows when your Power Automate function is PowerApps v2. Does not show if you are just using the PowerApps function.

[Pstork1]

Agreed, must be Power Apps v2 trigger and must be in a solution.

[Maltener]

For me this didn't solve the issue. I ran into the same problem, wanted to move a solution from DEV to PROD. 
On DEV everything worked with a few test users. On PROD only me as the solution's developer can use the embedded flows in the app. All other users receive the error you mentioned in your initial post. 

The affected flows all have a specific connection selected in the run only user setting.

Any idea?

[Pstork1]

Were the flows in the same solution as the apps that invoked them? And were they setup to use Connection References or did they use just Connections? Both of those need to be true as well. Moving the Apps and flows separately is what causes this issue.