Never, ever create a flow that looks like this:

Microsoft Flow Endless Loop

It is essential that you always set an attitribute 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!

Microsoft Flow Endless Loop Stats

The post Microsoft Flow Endless Loop appeared first on CRM Innovation - Microsoft Dynamics 365 Consulting and Marketing Solutions.