Flows Using Wrong Connection

I'm having an issue where my flows will not connect using the connection specified in the Flow editor. I have 4 MS SQL databases connected on the same server. Standard SQL databases, not Azure SQL.

I set up a test flow to execute a stored procedure in one database, then a stored procedure in a different database. The top procedure is configured to use DB1. The second stored procedure to use DB2.

Running the test on this flow shows me which connections it will try to use, and it reports using DB1 for both procedures. If I change the values in the test run interface it works properly when executed. However, it should be pulling from the connections I have selected on each procedure in the flow editor.

Re: Flows Using Wrong Connection

First of all, you need to ensure that the connection with these DB is currently connected, and the correct connection is selected when configuring the action.

Secondly, when executing Flow, you can click "Edit connections" to check if the corresponding connector contains all connections. If not, you need to switch to the expected connection.

For example, I have two Send an email actions. The accounts configured by connection are barrycao and barry2, but only barrycao is displayed here, so I need to replace one of them with barry2, as below:

Image reference:

Please take a try.

Best Regards,

Community Support Team _ Barry If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Re: Flows Using Wrong Connection

Thanks for the reply. I have confirmed the flow nodes are set to use the correct connections in the flow configuration.

When I run the test, the connections are replaced by different connections, just like in your example. Choosing new connections works... but that doesn't help me when the flow runs automated. The flow needs to use the connection set up in the configuration.

This is how it is configured:

This is how it completely ignores my configuration when I run the test:

Running this as a normal flow will fail because the stored procedure in IntegrationSupport doesn't exist in EPDS92.