Connection not configured for this service

(0) Share

Report

Posted on by SCTdan

604

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

Categories:

Building Power Apps

I have the same question (1)

All responses (26)

Answers (1)

Pstork1 68,707 Most Valuable Professional on at

Like (0)

Report

Have other users been added as Run Only users on the flows? The flows need to be shared with them in some fashion, but they shouldn't need to be co-owners.

Was this reply helpful? Yes No
SCTdan 604 on at

Like (0)

Report

They've been added as run only users, and the app is shared.

Question on run only users though- My trigger flows do not give me the option to add run only users, but the child flows do. Is that normal? Is that because the trigger flows do not have any service connections in them? They just set variables and call the child flow.

Was this reply helpful? Yes No
SCTdan 604 on at

Like (0)

Report

I think this is environmental, not just an issue with a single solution.

I created a new solution with a new app and a new flow. The app has a single button that calls the flow. The flow has a single compose action, nothing else.

Same issue.

If I create an identical app and flow outside a solution, works fine.

Was this reply helpful? Yes No
SCTdan 604 on at

Like (0)

Report

Related somehow- One of my flows will trigger (as owner), and trigger the child flow, but I get this

That's a connection to another user calendar. If I remove that action (Outlook Delete Event) from the flow, it'll run fine. Adding/removing/changing the connection doesn't help. I cannot find that connection reference anywhere.

The other processing flow is able to create calendar events using the same connection reference.

Was this reply helpful? Yes No
Verified answer

Pstork1 68,707 Most Valuable Professional on at

Like (3)

Report

I did some testing and found that flows with Power Apps triggers that are in a solution need to be shared with other users or they won't run. Since there is no Run Only User in Power Apps triggered flows you must share them as co-owners. Its the only way it works.

Was this reply helpful? Yes No
SCTdan 604 on at

Like (0)

Report

That seems to be the case now, but unless that just changed, my app had been working for a couple months without it being shared at all.

Was this reply helpful? Yes No
Pstork1 68,707 Most Valuable Professional on at

Like (0)

Report

Yes, I think that's a recent tightening. I've raised the question to the product team because I don't think its intended.

Was this reply helpful? Yes No
SCTdan 604 on at

Like (0)

Report

Yea certainly doesn't seem like it should be intentional. Hopefully they can shed some light on it, however long it takes to get an answer from them.

Was this reply helpful? Yes No
SCTdan 604 on at

Like (0)

Report

Full response from my ticket.

Strange he pasted in links to internal resources, but I'll leave them in in case a MS person needs to reference or something. Mods can remove if necessary.

As per the update's from the investigation team:

Looks like we had an outage for this:
https://portal.microsofticm.com/imp/v3/incidents/details/225055572/home
https://portal.microsofticm.com/imp/v3/incidents/details/230166578/home

These were both in earlier March and both are still open. Key details...

The issue here was found and addressed last week, however player was deployed with a version prior to the fix; upon discovering this, we stopped the deployment and rolled back to the non broken version. We have now re-deployed version 21024 but with the proper fix in place.

It reads like you have noticed this issue when they republished the app after making changes, they may have ended up on a player version that was having issues.

They may want to try an earlier version:
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/restore-an-app

Other mitigations are covered in the Investigations, much of which you have already tried. There are some limitations:
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/solutions-overview#known-limitations

It doesn't clearly state this issue but there is a hint that auth won't work the same way...

Flows in solutions don't support delegated authentication. For example, access to a flow is not automatically granted based on having access to the SharePoint list the flow was created from.

Owners get to run the Flow behind their user context so this would be bypassed. That wouldn't necessarily be the case for someone just shared with.

One last point, I think the child Flows may be a factor here based on this KA:
https://crmglobal.corp.microsoft.com/GLBCRMSUP/WebResources/crmee_/Pages/CrmGlobal.KnowledgeContent.html?data=articleId%3d36f23235-c26a-eb11-8116-000d3af8b049

It reports...

It is seen of this issue is that in some cases there is a flow with some dependencies, but 1 or more of those dependencies do not list the flow as a dependent and this causes our logic for connecting to flow.

Up next...

>> Best chances seem to be reverting to a prior version or republishing the app on a different Studio version.
>> Confirm the behavior when child Flows are not involved.
>> Confirm if you can repro this. Always possible this is now part of the design.

Was this reply helpful? Yes No
Abhishek Gawde 96 on at

Like (0)

Report

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.

Was this reply helpful? Yes No