I have created a flow that triggers when a record is inserted into SQL server (in Azure, not on-prem) and when I use the test mode and perform the trigger myself, the flow runs perfectly. The problem is when I leave the flow on and insert into the table, the flow does not trigger by itself.
I also have have a primary key/identity column specified in my table.
Edit: Testing while performing the trigger on my own no longer works, I have changed nothing with the connection.
Edit2: I believe I have narrowed the problem down to performing too many tests/inserts in a certain timeframe will mess up the connection and prevent the flow from triggering. The flow will be triggering when I change the connection on the the SQL Server trigger to a connection configured the same, but with a different name
Does your flow work well after you recreate the connection with a different name?
I haven’t seen such an issue, I will try to reproduce it on my side.
I'm having the same issue as originally described. The flow works when I choose test and enter a new row but will not work when just left switched "on".
Learn how to create your own user groups today!
Check out the new Power Platform Community Connections gallery!
Join us, in-person, December 7–9 in Las Vegas, for the largest gathering of the Microsoft community in the world.