PowerApps(V2) you may break your power apps triggered flow with changes on the added connections

[Rob-in-Dev]

So I'm replicating a Power App Instant Cloud flow, converting it to a Power App (V2) flow so I can include it with a Solution for deploying to another environment.  

In creating my new Flow, Power App (V2), I've copied everything word for word, condition for condition, everything is identical with an exception being that the Power App instant cloud flow's initial step doesn't have a parameter configuration option, whereas the Power App (V2) allows to add a variety of parameters.

In the Power App (V2) flow I created, I added a Text parameter to the first step of the flow.

As I proceed in the flow, I get to a "Get row (v2)" SQL command.  I've selected the use of a preconfigured SQL Connection that reaches out to an Azure SQL database with SQL Authorization.  

In the Power App flow, (not the V2), I can do this without error.  However with the Power App (V2) flow, I get an error in Flow Checker stating "you may break your power apps triggered flow with changes on the added connections".  

How am I supposed to create and use a flow, triggered by a Power App, that hooks to SQL if I cannot use a connection?

[Rob-in-Dev]

A little additional detail...

When creating a Manually Triggered Flow (From button on mobile (or whatever it says)), I have zero errors.  I'm trying to see if I can simply have the Power Apps flow call this mobile flow or if Power Apps can call the mobile flow directly, but it's weird that Power Apps (V2) flows throw connection errors and Manually Triggered Flows do not.

[Rob-in-Dev]

And it only gets stranger...

This Power Apps (V2) flow uses 2 connections.  A SQL Database connection (SQL Authentication) and a Twilio connection (Twilio Text messaging built by Microsoft).  

When I go back to rebuild the Power App V2 flow, I can use the Get row V2 action and the Update row V2 function without Flow checker throwing an error.

However as soon as I add the Twilio action, Send Message, Flow checker throws errors on all of my SQL actions, the Get row V2 and Update row V2 actions both show the error noted in the subject heading of this question.

Why would one connection, that's a completely different kind of connection, throw errors on all of my SQL connected actions?

[Rob-in-Dev · Accepted solution]

So I found the problem...  Using the Power Apps (V2) flow, your connection options are set to a setting of "Provide By Run-Only User".  Changing this to use one of my connections fixed this odd series of errors.  Steps are...

1.  Find the Power Apps V2 flow that is generating the error.

2.  Using the 3 vertical dots, go to the "Details" of the flow.  (not Edit flow)

3.  On the bottom right of the Details screen, there is a box labeled "Run only users".

4.  In the run only users box, click the blue "Edit" text.

5.  In the screen that pops up, your connections used by the flow will be displayed at the bottom.

6.  Switch the connection options from "Provide by run-only user" to the connections you're using in the Flow.

7.  Save your changes.

Note:  I had to do this change with my flow after I had SQL actions loaded into my flow.  I changed the connection in the details page at that point.  Then after I updated the connection in the flow's details for my SQL Server connection, I added my Twilio connection action.  I saved the flow again.  I went back to the Details of the flow, updated the connection option of my Twilio Connection now that it was displayed, and set that to the same connection I'm using in the Flow itself.  

Basically, at every step in building the flow, I add a connection using action.  Then go to the details of the flow, change how that connection is used by the flow.  Then add more content to my flow.  It's annoying but it at least got the flow working...

Now let's see if this all comes together nicely in a Solution Deployment.