I have this issue with ONE user. This user is an established employee who has used this app many times in the past. I have not made changes to the app in a couple of months. Now, this error appears 100% of the time.
What I did:
What am I missing??
Solved! Go to Solution.
So, since this thread is the first google search result, anybody here still searching for a solution?
Basically the flow which was working for all users properly, just broke for everyone except the owner. Is this an issue that Microsoft recently (February 2021) 'produced'?
Any hope on this now?
I do not have the liberty to create copies of all the flows at this point.
Solved creating new connection and using it in all the flows instead of the old one ( i've only SQL Server source ).
Then readding all the flows in the app it seems working like yesterday.
I had the same issue where my flow that was trigged from a PowerApps Button, worked for me (owner) but not for 2 users. They got the error message 'flowname'.Run failed: Connection not configured for this service.
What fixed it for me was:- (I've seen other posts where this hasn't worked)
The powerapps Button 'onselect' - that triggers the flow i disconnected the flow and then reconnected it, now it works fine for me and the other 2 users, to disconnect this is what i did:-
Selected the button that triggered the flow
Selected from the PowerApps menu bar Action
Selected Power Auomate, which then displayed all the flows, the top flow is the one associated with the button, on the ... by that flow Iselected remove from App.
Then from the list of flows selected the flow again to connect.
Fixed up the code on the button (as this wipes any code from the buttons onselect)
Then all was good.
Amazed that this is still occurring....
With me it is in a Canvas App inside a Managed Solution --> reconnecting App to Flow is not working and off course creating copies of Apps and Flows totally makes the Solution Concept useless from an Application Lifecycle Management (ALM) point of view.
If someone stumbles upon this like me and tear the hairs out trying to figure out why it does not work anymore even with simple flows etc.
What I ended up needing to do to fix this error that occured for some users was to follow the advice on this conversation
I also later got the exact same suggestion from MS support:
Based on the issue description which you have provide according to that I can understand that you want to run the flow through the apps , but some of the user not able to run it.
Could you please check that if you are blocked with any security roles. Please follow the below steps;
Users must be granted organization level read access on process (full green circle). This should be set on all security roles assigned to users that run flows.
You can either edit an existing Security Role or opt to create a new one just for this purpose.
So if you don't want to follow the thread above: