Automated (SharePoint Item Edit) Flow launching multiple times

[Anonymous]

Good day,

I have a flow that is triggered automatically when an item in SharePoint is edited/modified. 

I've noticed that the flow is triggered multiple times eventhough only 1 item was modified

Perhaps it will check all items and then match the condition to identify the edited iteam, then apply the flow details?

(my list can soon have over 3,000 items and this could delay the flow from execution)

Just need some clarity on this, thank you.

Screenshot below:

[RobElliott]

Hi @Anonymous, it would us work out what the problem is an a solution if you could post a screenshot of the steps in the flow.

Rob
Los Gallardos

[Anonymous]

Hi @RobElliott ,

Thanks for responding back.

My flow is quite straight forward:

• If a SharePoint Item is created or modified
  1. Check if the status is = Approved AND Data Matching is = "-"
  2. If YES, Proceed to further checks and actions
  3. If NO, Terminate.

I've attached a screenshot for reference

I just checked and the flow keep initiating even though nothing has been done on SharePoint - strangelt every few minutes it kicks off for some reason. Maybe if I understand the logic i could adjust accordingly

thanks in advance for your help 

[v-alzhan-msft]

Hi @Anonymous ,

The flow with trigger when an item is created or modified and be triggered as soon as the item has been modified.

Please modify the item by clicking the Edit field and then edit the item in the pop up window to prevent the flow for be triggered multiple times:

Best regards,

Alice       

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Hi @v-alzhan-msft , I am using powerapps forms on SharePoint however this should not really impact the behavior of the flow since it also just saves the edited item to SharePoint. Not sure how you recommendation would fix my issue?

Thanks

[Anonymous · Accepted solution]

So I found the issue is due to a formula.

I was checking if a date field is empy, but using an incorrect syntax, basically the formula always returned a false result and the date value was updated each time.

I've now fixed the formula and the runs only go once.

Below the date formula for reference:

Condition Flow:

not(empty(triggerBody()?['SUPPORTINGRECEIVEDDATE']))    is equal to   true

Regards