Answered

Dataverse row added trigger working for one flow but not another

(1) Share

Report

Posted on by RM-20051807-0

I have a flow that has been working for months that recently stopped responding to its trigger, which is when a row added to a Dataverse table. When a row gets added, the flow simply doesn't fire. It doesn't show any checks, failed or otherwise.

I built a second flow to test the trigger. It's in the same solution, uses the same connection, and is configured identically. It fires when a row is added to the table, but the first flow doesn't.

I tried deleting and rebuilding the trigger in the first flow - it still doesn't fire when a row is added.

I am completely out of ideas. I have tried rebuilding and refreshing everything I can think of. Why would one flow respond to the trigger when another doesn't, and they're configured identically? What can I do to get my first flow working again? It's an extremely complicated flow that took weeks to build, so I don't want to have to rebuild the whole thing from scratch.

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

Michael E. Gernaey 53,488 Super User 2025 Season 2 on at

Like (0)

Report

HI @RM-20051807-0

Well on the bright side... you could literally create a new flow. Add the trigger, then copy everything below the other and paste it into the new one. I cannot see your flow but yes you can do that.

I had that happen to me once, no matter what I did, the trigger was broken period.

Personally I would do what I suggested than fight with it.

But just for kicks

1. Is the trigger in both pointing to the same table

2. Do you have a trigger condition your forgot about and thats why its not firing

3. Did you try recreating a new Connection (please use references, not just connections) but a new one for the trigger to use

4. Dumb, but did you try turning it off and then back on.

5. Try exporting it and then reimporting it as another flow and see if it works

6. Do a Save As Copy, see if that one works

Let me know if anything helps or if you still need more help.

Was this reply helpful? Yes No
RM-20051807-0 6 on at

Like (0)

Report

Thanks for the tips, Michael! The triggers were configured identically, so they were pointing to the same table and using the same filter/condition (none).

I had tried all the rest, but it turned out #6, copy it using Save As and turn off the old one, worked!

Was this reply helpful? Yes No
Michael E. Gernaey 53,488 Super User 2025 Season 2 on at

Like (0)

Report

So glad it helped.

Lol overtime you just... trial and error find things even by accident lol

So glad its working for you now.

Was this reply helpful? Yes No