Unanswered

SharePoint "Changes" are constantly triggering flows

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

I have a couple flows that trigger from a change to a sharepoint list. Lately, these flows are triggering constantly without any input or change to the list. Looking at the version history of the triggering item, it seems to be constantly "pinging" that item as a change?

Even though there is no change to the item, Sharepoint is thinking that its constantly changing. I have no idea what is going on here.

Any and all help would be welcome!

Categories:

General topics

I have the same question (0)

All responses (14)

Answers (0)

Alex-W 315 on at

Like (1)

Report
Copy link

Link copied!

@LitLadLarry try creating a condition that must be true before the flow runs. For example, if Column A is equal to ABC, run the flow or else do nothing.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

I'm afraid that because one of my flows acts as a report of items changed, and it needs to trigger on almost all changes, this won't work well for me.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Even if I come up with a good condition to trigger from, sharepoint is causing the flows to trigger so often that they will eventually get throttled.

I turned on this flow for a few seconds and it trigger a dozen times.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Looking through these triggers more closely, the only field that shows as changed is the "Modified" column.

From the output of a Get Changes action:

Was this reply helpful? Yes No
Alex-W 315 on at

Like (0)

Report
Copy link

Link copied!

@LitLadLarry can you share a screenshot of the flow that is linked to this list?

SharePoint can do whatever it wants, but if the change does not pass the condition test it will not run.

Was this reply helpful? Yes No
RobElliott 10,397 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

You seem to be in the infinite trigger loop problem. You need to look at your flow and see whether you have an action that runs whenever the item is modified.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Here is most of the flow. I have a condition already but to evaluate that condition the flow needs to trigger and get those changes. The meat of the flows does not run, but the problem is that it's running off of nothing.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Could you please explain a bit more about this problem? The flow does trigger when an item is modified, but the flow does not modify any list items itself.

Was this reply helpful? Yes No
Ellis Karim 11,819 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Please share a screenshot of the "Get changes for an item or a file (properties only)".

Ellis
____________________________________
If I have answered your question, please mark the post as ☑️ Solved.
If you like my response, please give it a Thumbs Up.
My Blog Site

Was this reply helpful? Yes No
Alex-W 315 on at

Like (0)

Report
Copy link

Link copied!

@LitLadLarry the flow is triggering when an item is created or modified. I try to not to use this type of trigger because of the potential infinite looping issues. I recently had such an issue that created over 20K items on SharePoint over a four day period. For me, the issue was flows were in the queue and kept running. So, go to your flow log and change the view from All runs to Running. If you see any flows there, try canceling all of them to see if that stops the loop.

If your flow log is good and you do not have a long list of flows running and you are not able to create a condition, try create two new flows... one for when an item is created and the other for when an item is modified.

Was this reply helpful? Yes No