Unanswered

Random “Connection not configured for this service” error

(0) Share

Report

Posted on by Blaxy1

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:

Copied the flow with new name and connect again to power apps
Create the flow from scratch
Share the flow with others (I read this in other forum posts, but does it make sense?)

It’s very confusing because none of the steps above helped and I can’t find and other solution on the Net.

Categories:

Building Power Apps

All responses (8)

Answers (0)

Sort by

v-monli-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

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.

Regards,

Mona
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks for posting in the community @Blaxy1 - can you review the above reply and update the thread if it was helpful?

Thank you,

@Anonymous
abradford 6 on at

Like
a
(1)

Report
Copy link

Link copied!

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.
martinav 3,347 on at

Like
a
(0)

Report
Copy link

Link copied!

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.
karamjit 2 on at

Like
a
(0)

Report
Copy link

Link copied!

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
martinav 3,347 on at

Like
a
(0)

Report
Copy link

Link copied!

@karamjit ,

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:

https://powerusers.microsoft.com/t5/General-Discussion/quot-Connection-not-configured-for-this-service-quot-Error-when/td-p/273453
DawsB 5 on at

Like
a
(0)

Report
Copy link

Link copied!

Did any one managed to fix this issue?

This is the second time I'm facing this issue. Last time I was able to fix this by
- Removing the flow from datasource
- Removing the code that triggers the flow
- Save, Publish and close the app
- Open the app and re-add the code that triggers the flow. This will also add it to the datasource.
- Save and Publish
skydivertak 64 on at

Like
a
(0)

Report
Copy link

Link copied!

I see that this is an old thread, but we had this happen in October and once again just today. We have not made changes to the app or the flow.
Removing, reconnecting and saving fixes it, but we shouldn't be doing this with a production app!
Has anyone had this happen repeatedly, or had a possible solution?