Flows not being triggered by PowerApp "Connection not configured for this service"

[flow12000]

Hi

I have built several flows that run when various buttons are clicked in a power app. I am the sole Owner of the flows. All users in my organisation have access to the PowerApp. However, recently, users have been unable to run the flows from the PowerApp, triggering the following error"flowname.Run Failed: Connection not configured for this service". Users previously were able to run these flows from the PowerApp and even now some users can still run some of the flows but not other flows in the app. I've tried removing and reconnecting the flows in the PowerApp and then republishing but this has not solved the issue. If I make a user an Owner of the flow they no longer have any issues running the flow from the PowerApp. but I do not want all users to be Owners of the flow. Is this a new update? Does anyone know how to fix this issue?

I've attached an image of one the most basic flows that is still not functioning for general users, although they have the correct connections (ie. mail).

[P_Fry]

I am having the same issue. I have a managed solution app with flows that users have been using for months without issue. This morning, I have a user reporting in that they are getting the same error on all flows they've attempted so far. I have tried escalating this user to a Co-Owner of the apps and flows but no dice on a solve. I have other users with the same user permissions as the one getting the error that have no issue.

[v-bofeng-msft]

Hi @flow12000 :

If you don't share the flow with other users, they won't be able to call the flow.
If you don't want to give other users Owner permissions, then you might consider replacing the trigger with "PowerApps (V2)", which will provide a way of sharing called "Run only". You can share this Flow with other users in a Run only way.

Note: If the trigger is replaced, the stream needs to be re-added in the Canvas app

Best Regards,

Bof

[flow12000]

Thanks for the advice! It actually started working again for no particular reason when I tried this morning...(I didn't change anything just reloaded the app so I'm not convinced the flows can't be shared with users via power app using the v1 trigger). If I run into trouble again I'll try what you suggest though, thanks!

[rbn_nue]

Hi @v-bofeng-msft 

I'm actually facing a similar kind of issue posted here. 

Specific users are getting "connection not configured for this service" error. I'm sure it will work when the flows are shared with users. But my question is all these users are able to access the app without any issue in dev environment. Flows are not shared with them there. Only the app is shared (user access). Could you please let me know why it is not working when exported to another environment as managed solution?  

Thank you.