I have a flow that is connected to a large, heavily used Sharepoint O365 List. Up until late last week (I believe it was 5/25/17 around 2:30pm-ish), it worked like a dream. 100% success.
The flow is designed to pick up modified items, do a check against a "Status" field, and based on that, either send an email or skip. Due to the fact that I'm statusing, and on each status change I save the item, it kicks off multiple flows per item. I have 3 statuses, New, In Progress, and Completed. When it gets moved to Completed, it sends the emails.
Like I said, up until last Thursday, it worked like a dream. It would trigger on both in progress and completed, and run the whole flow on completed. A+. Well, silly ol' me introduced a second, smaller workflow on the same list to test something, as opposed to messing with my perfect child. Thats when the problems started.
I noticed my new flow only triggered about 2/3rds of the time. It would detect the "In Progress" save, but then never detect the "Completed" save. It wasnt erroring out, flows just was NOT triggering. Unfortunately, the trend has spread to my heavily used email workflow.
To get a sample size, I scrolled through my email to see what my sent box looked like. In 2 days and a few hours this morning, there have been a total of 337 items "Completed". Of those 337, ONLY 215 have triggered on the modify containing the "Completed". Thats a 64% success rate folks. Thats TERRIBLE.
Here is what I have done to troubleshoot so far:
No, the list name hasnt changed. Nothing significant has changed to the list. I havent modified the flow (outside of the connection user stuff). It simply went from perfect to garbage. Has anyone else experianced this, or can a mod/admin tell me a solution? I've done everything I can think of short of deleting the flow and starting from scratch, but I dont want to go through all that trouble and it still not work. It took forever to write, because I have several versions of HTML emails going on...
Correct its FS - we actually have another process, Tripwire, running that performs the same function, capturing file changes - our hope was that Flow could replace Tripwire. We plan to reconcile the two and I'll let you know the differences, but again, we can copy the flow and change only the servers/paths and see significant variations in expected versus actual output. It may be OS-version related?
ugh... spent an hour on this to find out its a known bug for YEARS.. and I thought I did something wrong.. i deleted, recreated, triggered (or so I thought).
Seriously this product has too many issues for my liking.
@dblyth I just sent some information to your email on this topic. My "when an item is created or modified" will run when I manually hit run or test --- but it gets stuck. It is not kicking off at all automatically upon creation or change as I would expect it to.
Thanks for checking with me. I "think" I send you a notification to ignore that. I'm still working on this but I think now it may be my error. I'll circle back with you for sure.
I'm good with this now. It was not related to the trigger failing rather -- I misunderstood the new menu for creating flows and selected the wrong one and I'd not put a button on my app to kick it off -- while I'd expected it to automatically kick off. I'm sorry but thanks for your quick reply.
Has there been a fix for this yet? I have spent days trying everything and rebuilding flows but have now given up where the flow only gets triggered sometimes on modify. 😞
Facing similar issue with Flow. The issue is random with my scenario and not consistent, sometimes the Flow skips updates happening to the list item in SharePoint Online list but other times fires. I tested this since 4 hours now and out of 20 updates it skipped 5-6 of them. But successfully fired at other times. Trigger is the same, connection is the same, list is the same.
So I would like to know the trigger dependecy detail, how can we check logs or find the trail of flow since update is made in SharePoint Online. Has someone faced similar random issue earlier? Looking eagerly for a resolution and cause of why it is happening.
Is it possible that there are multiple changes to the same item within a few second window? Unfortunately such changes in close proximity are batched together into a single flow run.
How are the items being modified as well? API calls? Other Flows? the UI's list editor?
Finally, is it possible that versioning is enabled and a new version has not been published when the changes are missed?
Any or all of these can impact whether Flows trigger and/or what changes they see when they run.
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
Are you new to designing flows? What is your biggest struggle with Power Automate Designer? Help us make it more user friendly!