I am attempting to build a flow that

  1. When an item is created or Modified
  2. It gathers email addresses using an HTTP request
  3. Does a select and join action to parse out an email address from a SP group
  4. Initializes two variables Date arrived and ordered.
  5. There is a condition check to see if an email is sent this is done by checking if a field is set to yes or no. if the field has yes it goes down the yes path.
  6. The Yes path doesn't have any actions in it. I just want it to go to the next step of the flow
  7. If the field is set to no, going down the no path it sends 2 emails then updates the item the field its checking to Yes
  8. Next step of the flow has a condition checking to see if a date fields value is null. if null the flow goes down a yes branch that has a do until loop. there is a delay then checks if a date field has a value. if no then it sends an email as a reminder. if yes, i have a set variable action that sets the initialize variable to true.

The first run of the flow is starting multiple instances of the same flow. The out come I'm looking for is.

  1. Flow runs when something is changed or modified.
  2. checks to see if it ran previously, if no send emails to recipients. changes field from no to yes
  3. if date field is empty send a reminder email until the date field has a value. once the date field has been updated it does the the next step of the flow what does essentially the same thing. It waits a duration of time for a different date field to be updated. sending a reminder until the second date field has been updated.
  4. one that field has been updated it sends an email letting the submitter know that the field has been updated.

First half of the flow

first condition that checks if email sent field is set to yes

Condition that checks if the first date field is empty

Do until loop that runs until variable is true, delays for a set time, gets item id from trigger, then checks if date is null. if null sends email. if not null sets variable to true

Back to the initial issue. The flow starts to run multiple times. One right after another. Even when the date field has been populated. It will start two or more runs and send reminder emails once every minute even though I have it set to 5 min.

I'll update the date field but only one of the flows will complete successfully. I'm unsure where the logic in my flow breaks down. I could really use some help.

canceled flows

  • There is almost a loop that even when the conditions are met it keeps going.
    – Mile T.
    Commented Oct 1, 2023 at 22:17

1 Answer 1


The reason that cause your flow to trigger frequently is: You used When an item is created or Modified as the trigger condition, but you also used Update item.Update item and When an item is created or Modified.

If you use the same list, then there will be a loop trigger problem. If you want the flow to not be triggered in a loop, you can avoid this problem by setting a Trigger condition.

Here is a link about trigger condition for your reference:


However, the conditions under which Trigger condition can be used are limited. If it does not meet your needs, it is recommended to add a Condition after When an item is created or Modified to avoid problems caused by Update item.

  • Has this method been helpful to you? If you have any further questions or concerns, I would be more than happy to assist you. Commented Oct 17, 2023 at 6:54

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.