Hello,
I have a flow in which when a value in a field is modified, sends a Teams post to a user and updates a field in the SharePoint list. Yet it continuously runs and send a post for the same updated item and won't stop.
Thanks in advance.
Announcements
Hello,
I have a flow in which when a value in a field is modified, sends a Teams post to a user and updates a field in the SharePoint list. Yet it continuously runs and send a post for the same updated item and won't stop.
Thanks in advance.
You could add a new Yes/No column called "UpdatedByFlow" to your SharePoint list, with the default being set to No. When you update the SharePoint item, set UpdatedByFlow to Yes.
The trigger condition would be something like:
@equals(triggerOutputs()?['body/UpDateByFlow/Value'], 'No')
and it will only trigger if the UpdatedByFlow is no, preventing the infinite loop.
See: Infinite loop when an item is updated post and
Hope this helps.
Ellis
@ekarim2020 The flow is triggering just fine and the value is exact 'Completed'. But it still stuck in a loop. Doesn't look like the trigger is working. This is a choice field with the determining value "Completed". Once the other column in the SharePoint list is modified, it sends another post.
Check: The text in the trigger condition will be case sensitive.
In my flow below, the trigger is based on the from email address. The email arrives as AlexW@ so the flow triggers. The flow does not trigger if the from address does not match AlexW@, for example alexw@ will not trigger the flow:
So in the trigger condition I can add the toLower() function to convert the From address to lower case before testing for my condition alexw@########.com
Hope this helps.
Ellis
@ekarim2020 So I added the following as a trigger to the SharePoint item modify and its still repeatedly shooting off.
@equals(triggerOutputs()?['body/Status/Value'], 'Completed')
Any suggestions? The flow needs to update another field in that same item.
One option: to add a condition to your trigger so it only activates when a certain condition is met (eg. only trigger the flow if the ID column is empty, does not contain a value):
A simple way to create a trigger condition in Power Automate
https://tomriha.com/a-simple-way-to-create-a-trigger-condition-in-power-automate/
and
Tip : Using Trigger Conditions in Power Automate
https://powerofpowerplatform.com/tip-using-trigger-conditions-in-power-automate/
Yes, this is because your trigger is waiting for "When an item or file is modified", then your flow executes.
But in your flow you are also MODIFYING the item or a file, which means that your flow is trigger again (item or file has been modified) ... and so on.
Ellis
Michael E. Gernaey
497
Super User 2025 Season 1
David_MA
436
Super User 2025 Season 1
Riyaz_riz11
244
Super User 2025 Season 1