SQL Server Connection and Flow are not playing nice together to say the least. Have a flow that WORKED! Yet today, failing on ...
Could not find stored procedure 'dbo.SynchSourceLogInsert'.
clientRequestId: 13063526-211f-479d-93de-cf2701ce0dde
Yet flow allows me to configure the step just find so it surely knows it exists when I configure it. But fails when I run it.
Issues with SQL connector are CONSTANT!!!!! These really needs some attention.
Hi @mcolbert ,
Please try to check the connection status in Connection list and fix it here:
For further flow issue, please post in Flow community here:
https://powerusers.microsoft.com/t5/Microsoft-Flow-Community/ct-p/FlowCommunity
Regards,
Mona
This is not the problem. The SQL connection is fine. And when I say teh connection works in design byut fails when running I mean the following;
I edit the flow
click the elipsis on the stored procedure step and shows my connection selected, if I clkikc the drop down onb the stored procedure name, it shows a correct list
I then click save & test
Flow fails with stpored procedure not found
The run environment seems to be picking up a different connection.
User | Count |
---|---|
140 | |
133 | |
80 | |
75 | |
74 |
User | Count |
---|---|
210 | |
199 | |
71 | |
66 | |
55 |