Power Automate Flow triggered from Canvas App fails due to "Connection not configured for this service"

[bianzi]

Hi,

I am facing the issue with running power automate from a canvas app with the error message "connection not configured for this service".  This is working fine in our test environment. However, it fails in production environment whenever running from a canvas app. Even the owner of the flow is using the canvas app, the error still occurs. If the flow is run in test from Power Automate, it finishes successfully.  

We have actually exported the solution with the canvas apps, cloud-flow, etc. in unmanaged mode, then imported to production and modified the configuration to point to appropriate sites. 

I have found some existing posts regarding this and tried the suggested solutions, but still no luck.

What I have tried so far is as follows.

- Re-configure the connection references in the flow

- Set the security role that the execute user is assigned; Grant Read access to Process table

Is there any other possible solution I can try with this issue?

[AmeerJab]

Hello,

Using flows in power apps is in some way tricky are you taking the user credentials when he use the app or did you set a service account that the connection is connected to?, i would also suggest re-creating the flow from inside power apps.

[bianzi]

Hello,

We have set the service account for the connection.

>re-creating the flow from inside power apps

Do you mean that we should comment out the part to run the flow in the canvas app, remove the flow and and set it back again?

[AmeerJab · Accepted solution]

yes i would suggest re-building the app from inside power apps, when a flow is triggered from inside power apps it uses the user as the connection to the flow, i would suggest looking into this solution by jhall https://powerusers.microsoft.com/t5/General-Power-Automate/Connector-asking-for-credentials-when-lau...

[bianzi]

We have not designed to run the flow by the user who is using the power apps. Instead, the credentials of the generic account is used. Do you suggest we use the credentials of the user?

[AmeerJab]

it depends on the use of the flow ex: 

if the flow supposed to send an email it will be sent from the user outlook also if it’s accessing a source the user doesn’t have access to it will fail.

how i handle the flows that i need to be triggered from a button is i trigger it using dataverse when a record is added or modified or i can set a new column in a database that is connected with my use and set this column value to be run flow and once the flow is done i set it to none and in power apps i use patch to update the column with “run the flow”, i do also recommend if you wanna use dataverse as trigger in the trigger settings you can create a trigger condition and set it to be inly triggered when the column value is equal to run the flow

[schphi]

Do I understand you correctly here, that you suggest that there is a difference if you create a flow via make.powerapps.com=>solutions=>New on the one hand and if you create it from within the canvas app editor on the other hand.

I get this error on a regular basis from new users. Existing users don't seem to have problems. When I hear of it, I open the Canvas App (luckily unmanaged), remove the flows and re-add them again, save and publish. 

This usually "solves" the problem. But this happens again and again and it leaves a bad impression with the users.