Add me to the list. I can't get any reliable performance out of "When a file is added or modified (properties only)" trigger. We're on the free plan, but I've let it sit overnight and still no action. Sometimes works, but usually not. What's up with this, MS? Please fix?
Same problem here. On Create and Modify SharePoint Item trigger works fine on test, but not consistently in practice. The flow shows as skipped, even if a field in the item has changed. Sometimes a modification of a future, separate item will trigger a previous stalled flow as well.
This issue is plaguing me on a new project, really frustrating. Just re-save the flow and it will trigger any backed up runs immediately. Clearly some sort of bug, can't believe it's still an issue.
Yep my Flows runs aren't even showing up in the log, then I edit and save the flow and it triggers all backlogged flows.
I have two Flows referencing the same SP list; one triggers when a "new item is created," and one that triggers "when an item is created or modified." The former works like a charm, the latter rarely fires.
I've seen some MS reps say in another thread that this could be due to how SharePoint batches modifications/changes to SP list items, and other threads where it's attributed to how often Flow/PowerAutomate will allow recurrent triggering. I've also seen it explained as a bug.
Does anyone with the PA team know which explanation is correct? An answer to this alone would greatly help how I design my Flows and how much time to invest.
I am in testing right now, so I am editing list items and testing flow triggering at a fairly rapid rate. If I'm simply testing with too short of a window for either SP or Flow to catch, that'd be helpful to know as well.
I was told it could take 15 minutes or longer at times depending on the type of subscription you have.
Btw, my flow always runs now within a 15 minute window max.
Well that's encouraging. I did test the Flow with longer window of time between modifications and it seems to have worked. Do you know of any official documentation from Flow about flow run time frames? Thanks
It says here that if you have the free plan, flows are queued to run every 15 minutes. I guess that solves it
The time has come: We are finally able to share more details on the brand-new ranks coming to the Power Automate Community!
We are excited to announce the launch of Power Virtual Agents Community. Check it out now!
We've updated and improved the layout and uploading format of the Power Automate Cookbook!
Fill out a quick form to claim your user group badge now!
The top training and networking event across the globe for Microsoft Business Applications