Power Platform Community Forum Thread Details

MS365 A1. I created a SPO list, with only 2 items. Main columns (among others) are Priority (choice, values: 1,2,3,4) and Progress (choice, values: new, working, paused, cancelled and finished). Then I created an automated flow triggered by updates (only) on its items (columns limited by default view, "All Items" - btw Priority and Progress are both set to be shown in this view).

Then I turned it off.

Fine. My need is to change the Priority of an item to "9" (ok, I know, "9" is not in the Priority column "choice values", but I assume it's not a problem when to run) whenever its Progress is updated to "Cancelled". Quite simple.

Hence I added one Condition and one Update Item actions to the flow (it's in portuguese but easy to infer in english):

I turned the flow back to on, waited 2 minute or so and checked the flow run history. It showed it had run even though the list was NOT modified 😕 (started "1 minute before"):

So my first question is: WHY the flow did run when it's turned back to on even though the list wasn't modified?

All right. Now back to the list, it's like this (just 2 items):

Then, I modified the Progress of "test 3" item to Cancelled:

I left as that for some 10 minutes. And as I went back to the flow run history ... it had been running several times - almost every 1 minute or so 😕 Even though I have updated the list only once since that!

So my second question is why the heck the flow keeps being triggered like this despite the list not being updated?

Seems it has to do with items with column Progress = cancelled (it satisfies that flow condition). Because, as I dug into, I then changed "test 3" item from cancelled to paused and the flow run history showed it hadn't run thereafter 🤔. Like, the flow keeps being triggered while there is "at least" 1 item satisfying that flow condition (progress = cancelled) even though I do not change anything in the list... 😖

Thanks in advance for any enlightment.

Categories:

General topics

I've found the answer for my 2 questions. Despite the sharepoint builtin trigger "saying" "when an item or file is modified", actually it's created "internally" as a recurrent trigger with 1 minute interval 😕 I verified this as I digged a few more and went to flow editor to exhibit the trigger code :

So... now a new question arised: is there any form to trigger a flow ONLY when list items are really updated?

I've read this article but it seems although it can relieve some processing load by triggering a flow only on a "condition", the flow trigger kind still would be scheduled (would trigger it every other minute and check the condition). The run history would still be filled with tons of records of executions (I mean, useless for debugging) 😕