You’re offline. This is a read only version of the page.
32
I have a flow that sends an email upon a SharePoint item being modified.
I turned it off to run a PnP PowerShell script to update the list.
Then I turned it back on -- and it sent out hundreds of emails.
But it was off when I ran the script, and I didn't turn it back on until the script was completed (and maybe a minute or more afterward).
Has this happened to anyone else? What did I do wrong? Why did it trigger even though it was off?
Thanks Scott. It'd be helpful if Microsoft updated their documentation to mention that.
I can only find it obliquely mentioned here, under Flow Runs. Do you have a better source? I'd be nice to present that to the incident board.
When you build a Power Automate flow to be triggered for an item, or for creating or modifying a file, Power Automate periodically checks for changes in the list or library, configured in the flow's trigger. In most cases, if there is a single change in the list or library, the flow run may occur within minutes after that change. However, expect that the flow may gather more than one change in subsequent flow runs due to the time between the flow interval since its last valid change, or subsequent edits to an item or a file.
@JosephCrockett Depending on your license, it could be a number of minutes before a Flow trigger fires. I believe up to 5 minutes for a standard O365 Power Automate license You need to give it at least that much time before turning your Flow back on.
#1
WarrenBelz
146,645
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
65,997
Most Valuable Professional
Share
Report
All responses (
Answers (
