Flow Run failed: Connection not configured for this service - only a single user affected!?

[JamesM]

I have a user getting the above error whenever the screen navigation kicks off this associated Flow. (GetGroupsForUser) which just gets some data from Azure Table Storage and returns it to the app. He is the ONLY user getting this error, and it occurs on both Windows Desktop and his iPhone. He has closed and re-opened the app, and uninstalled and re-installed PowerApps on his phone. Message still appears. 

I can't find a failed flow execution for this user in the Flow history however, and other users including myself are using this flow fine? Could someone please assist to invsetigate this? It's driving me batty. 

[v-monli-msft]

Hi @JamesM,

Have you made sure that you have shared the flow with this user in Flow site? Also, all included connections are shared with this user too?

Regards,

Mona

[Anonymous]

@JamesM is the user still getting that error message? Also let us know if the above response was helpful

Thanks!

@Anonymous

[Rackabajsarn]

I also have the same problem. This is with newly added users to the organization. Not sure what you mean by sharing the flow? the only option is to make it a team flow and give the user rights to change it?

[ppicard]

Exactly the same problem without any solution

[abradford]

Is there any know solution to this problem? I have several PowerApps flow triggers in my app and it seems to be completely random if it works or doesn't. 

[Anonymous]

I am also getting same error. Did anyone found the solution to this problem? 

[bloodoff]

Same problem here.

[serastpan]

Hi,

I am having the same issue. I have read I have to make the users admin of the connection which is not ideal. This seems to be an ongoing issue MS don't know how to solve.

I would appreciate if you could have a look at it as it is making Powerapps very unreliable.

[bloodoff]

@serastpan  Making a user an admin wasn't the solution. Try to make a copy of your flow and then replace one with another. Making a copy fixed that issue. I agree it is a bit frustrating.