skip to Main Content

Microsoft Flow Endless Loop

Never, ever create a flow that looks like this:

Microsoft Flow Endless Loop

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!

Microsoft Flow Endless Loop Stats

Full disclosure – this was done specifically for demonstration purposes of what not to do.

This Post Has 4 Comments
  1. Hi Jerry, does setting an attribute filter tell the flow only to run when that particular field is updated?

Leave a Reply

Your email address will not be published. Required fields are marked *

Back To Top