Power Platform Community Forum Thread Details

Hi All,

Yesterday, a flow completed actions (send an email) on 3x items from my sharepoint list, even though the flow RUN shows it did not. I know that sounds crazy - has anyone else had this? Any ideas of how to troubleshoot? I've attached a copy of the run for one item, where you can clearly see it didn't meet the condition step so proceeded down the 'no' side, as it should have. However, I have the email that is triggered by the 'yes' side as proof it executed down the 'yes' side.

What the flow does:

When a sharepoint list item is created or modified, get the changes that were made. If a specific column has changed to a specific value, and another column is equal to a specific value, proceed down the 'yes' side. If not, do nothing.

Down the yes side, get items from a different list that match items in this list, and use data from both lists to populate an email and send it.

What I have already tried:

Investigating the flow runs. Because I have the time stamp on the email I do know which specific run this was, and for which item. The specific flow for one item was triggered 4x in the 24 hour period and each time the run history shows it proceeding down the 'no' path each time, and yet one of those 4 runs resulted in the email.
Checked the sharepoint item version history. At no time in the past 24 hours, or even the entire history of the item, were the values meeting the condition step changed. So, it was triggered due to changes in other columns, but none of the columns relevant to the View in the 'Get changes' step, nor of course the Condition step. So it is fine that is was triggered, and it should have progressed down the 'no' side, which it clearly did 3 times.
Checked with IT if there was a Power Automate outage/glitch at the time of the email (not that they're aware of). (The time was 8.38pm on 24th Oct AEDT).
Checked (just with team members) that nobody else has a version of this flow that is somehow incomplete and turned on (answer pending but verrry unlikely)
Note that this flow has executed correctly hundreds of times for months, including 110 times after the 3 incorrect items I mentioned above. Each time, the run matches the behaviour, and executes as I would expect i.e. there is nothing wrong with the condition step in the flow.

Any help/advice or experience with this would be very much appreciated. I know it's a weird one.

Thank you!