Power Platform Community Forum Thread Details

Ive noticed a few posts in hear mentioning a "Not configured for this service" error when trying to start a flow form PowerApps.

Ive recently been plagued by this for certain uses and after much pain going through the motions (no response from here either) I think ive found a bug.

Firstly my app was developed in a solution and has a simple flow connected via a button that gets a SharePoint item and then sends an email using the Office 365 Outlook connector, as the flow was created from the App using the power automate button, so the new flow Connection references were automatically used, although they did not show in the solution.

The app was shared to the organisation with no issues, however for certain users, when clicking the button to start the flow from the nothing happened except showing my error handling that was expecting a response from the flow. After much digging around I found that users the effected users were getting a Not configured for this service error which i could see if I made them a co owner of the app and looked at the error.

I tired everything form removing the flow from the app and re-adding it (Which you have to do if you change the flow in most ways of it breaks grrr) to actually re making the flow from scratch. In the end I did some more research and discovered that I probably needed to add connection references to the solution naming them appropriately and changing the connectors in the flow to use them, then remove from the app, re-add the re-share the app. I thought this was going to fix the issue but it didn't and I spent the last 2 days pulling my hair out trying ever permutation of deleting adding creating connectors until I found a strange solution.

Solution! For the affected users (remember its only a few users having this issue), I simply made them a co owner of the flow that wouldn't run, the flow ran fine then for the user and I found removing them as a co owner the flow still ran fine with now issues for them.

There is obviously a permission bug going on here somewhere in the chain, so for any one who get this strange issue try it. MS please look into this more details can be provided.

Thanks