Microsoft Flow Endless Loop
Never, ever create a flow that looks like this:
It is essential that you always set an attribute filter when using the Common Data Service When a record is updated trigger!!! If for some reason the business logic won’t support any filtering then it is essential that you do not have a downstream action that updates the record that caused the trigger to fire!!!
Why not? Because before you can say 1,2,3, your flow analytics will look like this or worse. Yup, you are reading that right, 421,104 flow runs in 2 days!
Full disclosure – this was done specifically for demonstration purposes of what not to do.
This Post Has 4 Comments
Well, the good news is that the executions were all successful!
Full disclosure – this was done intentionally to document the results. I am usually not this careless. 🙂
Hi Jerry, does setting an attribute filter tell the flow only to run when that particular field is updated?
Ian, That is correct.
Jerry