Connection not configured for this service

[SCTdan]

I'm at my wits end trying to figure this out.

I have a solution containing a powerapp and a few flows.  It had been working fine up until I made some changes last week.  These changes did not include any addition or modification of any connections, merely cosmetic.

After those changes, it worked just fine on my account, but everyone else started getting the 'Connection not configured for this service' error.

The powerapp only directly calls 2 flows.  Each of those calls another child flow to do the main processing.

I have:

-Deleted / recreated all connections and connection references

-Removed / Readded flows to the powerapp

-Recreated the trigger flows

-Deleted the solution and reimported

-Made a trigger flow that did literally nothing but set a variable

-Tested with a brand new user account, no connection history

-All connections show connected

-All connection references show status of Off (appears to be normal?)

I can give other users owner on the flows and it'll work fine, but that is obviously  not an ideal solution.

The most frustrating part here is there's no indication where the problem actually is.  

Any suggestions are very much welcome

[abhishekgawde]

Hello @SCTdan, @Pstork1 

Was this issue resolved by any other way except for making the end-user as the owner.

I am facing the same issue for all of my applications.

[SCTdan]

My ticket is still open, but we've basically tried everything with no luck.  I keep asking if they've asked the power platform team (easier said than done I'm sure) if this change was intended or not, but no direct answer on that.  They just keep having me try different things.  

[sammybridge]

I've now ran into this issue as well and it is causing major issues. Is anyone any closer on resolving it? I've found making users System Administrators (purely for a test) fixes the issue, so I'm guessing something in the Basic User Security Role does need changed, but I can't work out what

[sammybridge]

Hi guys,

Just an update on this, I have added the following two properties, both under Customizaton, to the Basic User Security Role and it seems to have worked:

[mate_toth]

Thank you for posting this, @sammybridge.

It also works for me with these settings! 

[mate_toth]

@sammybridge: Update on my previous message: it does work with "not first time" users, new users are reporting that they get the error when they first use the app. Once they do a refresh or open the app the second time, it works.

Did you come across a similar issue?

[sammybridge]

@mate_toth I haven't had this reported to me from the client I done work with. I'm assuming it isn't an issue in my instance though as I put the change in over 6 weeks ago and haven't had any reports of this happening since then

[zerou]

What and where is this?

[powerbug]

Hi - I had the same problem and on Flow details page I added users "Flow run only" bit in the bottom right and it worked! they don't have to be co-owners

[DeeTronSEAM]

I was experiencing the same problem but even when I added user entries to the flow's "Flow Run Only" setting it didn't work.  Then I looked at the flow inside its deployment Solution and drilled down to the Solution Layers for it (i.e. from the more items menu: Advanced > See solution layers) and noticed it was showing an unmanaged layer on top of the expected root/single managed layer.  Once I removed that layer, the flow started working without the error the users were getting before.  I've had the same problem with (Canvas) apps after deployment to production and chalk it up to the learning curve I'm going through with Solutions.  So I'm not sure what I did that caused that second layer (i.e. the unmanaged layer) to be applied to the flow, but I've learned enough to know that such "top coat" unmanaged layers block changes/behaviors/mods I'm expecting to be pushed out to production via the solution import.  Just throwing this out there in case somebody else finds it handy.  If nothing else, I concur with @powerbug that it is NOT necessary to add end-users as Co-owners to the flow....thankfully.