I have an issue with a flow which is triggered from PowerApps.
We are using this flow is for inserting mass data to Azure SQL table, because the Patch and Collect functions are extremely slow when inserting multiple rows.
So there is a text box on a hidden screen, where the insert SQL text is dynamically built by the Concatenate function and this text is sent by Flow to Azure SQL.
We are using the app from 14 iPhones and it was working without any issue in the beginning.
Around a month we get the “Connection not configured for this service” error message randomly.
It works perfectly from my phone and browser but from other phones with 40-60% success.
I can’t see any error message in Flow, because this issue happens at PowerApps side.
What I did:
It’s very confusing because none of the steps above helped and I can’t find and other solution on the Net.
Hi @Blaxy1 ,
Where did “Connection not configured for this service” displayed? PowerApps or Flow connection? Please try to find the connection that has this error in the connection list here:
Then try to fix the connection in this list.
Hope this could help.
Has anyone figured out the source of this problem? It appears to be completely random as I have triggers that work inside the app and triggers that give me the “Connection not configured for this service” error. The only solution that I have found that appears to be working is granting user owner permissions on all flows - which opens up a new set of problems.
I have one user getting this today, and two other users two different errors... 100% failure. Cant help to think its not related to a revision rollout that happened sometime last night. My PA shows a new version number today, and icons for SP also are different today.
Getting the same error from a power app that is being used by 20 so users.
Run Failed: Connection not configured for this service.
Half of the users keep getting the error messgae on same button that runs the flow, where other are having no issues.
This error is in the power app trying to communicate with the flow. All other flows are working fine for all
This was a very odd problem that only affected a single user. I did not come to any resolution that made any sense. It simply quit giving me a problem after I did some basic App cleanup. I didnt change anything, but removed some development screens, etc.
Here is my thread on the issue:
Featuring samples like Return to the Workplace and Emergency Response Applications
We're excited to announce our first cross-community 'Can You Solve These?' challenge!
Reopen responsibly, monitor intelligently, and protect continuously with solutions for a safer work environment.
We are excited for the next Super User season.
Features releasing from October 2020 through March 2021