Unanswered

SQL Connection failed when editing Flow - "Test Connection Failed"

(0) Share

Report

Posted on by martinav

3,340

I have a flow that works. I need to edit the flow. When I edit, an error appears over the SQL Get Rows action"Test connection failed". It will not let me save the flow due to this error. I have a feeling this has something to do with the new licensing. I get completely lost in these details of licensing. I'm worried. That all of this is going to become suddenly hyper-expensive.

https://docs.microsoft.com/en-us/power-platform/admin/powerapps-flow-licensing-faq

Like I said, when i run the flow, it works fine. Also, connections look ok.

Can anyone shed some light on this?

Categories:

Using connectors

I have the same question (0)

All responses (4)

Answers (1)

martinav 3,340 on at

Like (0)

Report

This is also happening with new actions.

Was this reply helpful? Yes No
martinav 3,340 on at

Like (0)

Report

More info I found:

https://powerusers.microsoft.com/t5/General-Power-Automate/Flow-SQL-connector/m-p/387572

Issue is... how much is this going to cost? I dont think you can even get an automate plan yet. Trial only???

Was this reply helpful? Yes No
v-litu-msft on at

Like (1)

Report

Hi @martinav,

It seems like the issue is caused by the SQL server connection change into a premium connector.

I find your first reply is using Get row action, this action has been deprecated, it seems like the action was created before the SQL connector changed, so you can see it still exist in your Flow, you can delete it and try to use Get Rows(V2) action.

https://docs.microsoft.com/en-us/connectors/sql/#actions

I just tested on my side to use Get rows(V2) to get all rows of a SQL table, the connection is old, but it works well, so maybe the error in the reply 2 is caused by the connection itself, changed gateway, changed password, etc. You can reconfigure it and try it again:

And you are search the license details, this is the PDF file of the licensing guide, you can download it to see more details.

https://go.microsoft.com/fwlink/?linkid=2085130

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

Was this reply helpful? Yes No
Verified answer

martinav 3,340 on at

Like (0)

Report

I cannot put my finger on exactly what happened, but after messing around in the Flow, I went to my connections, and the connection was gone! I know it was there before, because the flows were working fine just prior to my attempt to edit. I even tested it after the failure to edit and save and it was still working...

Regardless, I know I did not actually delete it from the Connectionss list. Anywho, I recreated the connection, and recreated the action. All is well.

I actually have about 70 flows. About half use SQL actions. Once I recreated the connection, there was no problem in any of the other flows. Most of those use the V1 actions. I'll keep an eye on it, and move to V2 only if things start showing some signs of instability. I have learned thorugh experience that if things are not broke, DONT try to fix them. It will only cause you more trouble!

Thanks for the comments!

Was this reply helpful? Yes No