Stop trigger loops when SharePoint item is modified

(1) Share

Report

Posted on by ROSEBLACK

205

Hi Everyone,

I have a SharePoint Lists that keep data up-to-date for approval comments (when the other is modified).

However, this causes a loop, is there a way to prevent this?

Thanks a lot!

ROSE

Categories:

Building flows

I have the same question (0)

All responses (6)

Answers (1)

ronaldwalcott 3,847 Super User 2025 Season 2 on at

Like (1)

Report

Look at Get started with triggers - Power Automate | Microsoft Learn which explains how to add conditions to the trigger

Was this reply helpful? Yes No
ROSEBLACK 205 on at

Like (0)

Report

I have read the topic and follow the steps.

It's not working for my flow. Your advise pleaseronaldwalcott?

Thanks a lot!

ROSE

Was this reply helpful? Yes No
creativeopinion 10,502 Super User 2025 Season 2 on at

Like (1)

Report

@ROSEBLACK The equals operator looks for an exact match. To learn more about how to use Trigger Conditions in your flow and how to avoid infinite loops, you might be interested in the YT Tutorials linked below:

♾️ ♾️ Fix Infinite Loops ♾️ ♾️ | 3 Ways to Avoid an Infinite Loop in Power Automate

In this Power Automate Tutorial I’m going to show you 3 ways to avoid an infinite loop. Keep in mind that there are more ways to avoid the infinite loop than what I’ll cover in this tutorial—choose the solution that works best for you.

IN THIS VIDEO:
✓ Understanding What Causes Infinite Loops
✓ Avoiding Infinite Loops with the Recurrence Trigger
✓ Filtering to Return Files Only in Power Automate
✓ How to Output a Total Count in Power Automate with the length() function
✓ Using Trigger Conditions to Prevent Flow Re-triggering
✓ Leveraging Service Accounts to Avoid Infinite Loops

----

4 Ways You Can Use Trigger Conditions in Your Microsoft Power Automate Flow

Trigger conditions can be set in most flow triggers. These conditions you set must be true for the trigger to fire.

In this Power Automate tutorial, I’m going to show you how to use trigger conditions in your flows to control when your Power Automate flows trigger. If your plan has flow run limits—you can avoid triggering your flows unnecessarily by using trigger conditions.

I’ll cover four different flow examples that would benefit from trigger conditions:

⚡️ Triggering a flow when a column is changed to a specific value
⚡️ Triggering a Flow When an Event Updated or Deleted
⚡️ Triggering a Flow When a New Folder is Created
⚡️ Triggering a Flow When a Specific Email is Received

I’ll also show you a trick on how to easily create the expressions needed and give you a few tips on how to troubleshoot your flow.

IN THIS VIDEO:

✓ Four different flows that would benefit from trigger conditions

✓ What is a trigger condition?

✓ How to add a trigger condition to your flow

✓ How to trigger a flow when a column is changed to a specific value

✓ How to trigger a flow when an event is updated or Deleted

✓ How to trigger a flow when a new folder is created

✓ How to trigger a flow when a specific email is received

✓ How to troubleshoot a trigger condition

✓ How to prevent case sensitivity issues with a trigger condition

✓ How to use the filter array action to easily compose an expression that can be used in a trigger condition

Hope this helps!

Consider giving me a ❤️ if you liked my response!

👉 Level up your Power Automate skills by checking out my tutorials on YouTube
👉 Tips and Tricks on TikTok and Instagram

Was this reply helpful? Yes No
Verified answer

Michael E. Gernaey 53,493 Super User 2025 Season 2 on at

Like (1)

Report

Hi @ROSEBLACK

So to be clear, you are modifying the same file that has been triggered in the Flow Trigger?

If that is so, then you have to come up with a way to make the trigger ignore it.

So my questions are

1. What field is getting changed?

2. Is there a way (just think human speak not computer expressions) to check if a Specific Field has just been changed.

For instance:

If you had a Status Column.

Its default value is No

When someone updates it to Yes you can:

Use the GetChanges action, right after the trigger.

You can then Check if the specific field has changed (our Status Column). You can also check if the value is Yes.

So you would do

Trigger

GetChanges

Condition Action (to check if the specific column has changed, AND you can validate if it was changed to Yes or not)

If condition 1 is true, and condition 2 is true (meaning our Status Column changed AND it was changed to Yes), we can made the changes

but if condition 1 is false (no one made Status Column Change), then don't trigger the code, as you won't need to do anything

The business logic depends on me understanding what you need to do 1 time, and never again so we can block it from doing it non-stop

Was this reply helpful? Yes No
ROSEBLACK 205 on at

Like (0)

Report

Dear @Michael E. Gernaey

Thank you, let me try on this.

Thanks a lot!

ROSE

Was this reply helpful? Yes No
ROSEBLACK 205 on at

Like (1)

Report

Michael E. Gernaey

creativeopinion

ronaldwalcott

I think the issue has been fixed.

Correct Trigger Conditions:

@equals(triggerOutputs()?['body/{ModerationStatus}'],'Pending')

Thanks a lot!

ROSE

Was this reply helpful? Yes No