Flow not getting triggered on every change to SharePoint list items

%3CLINGO-SUB%20id%3D%22lingo-sub-276078%22%20slang%3D%22en-US%22%3EFlow%20not%20getting%20triggered%20on%20every%20change%20to%20SharePoint%20list%20items%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276078%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20experiencing%20issues%20with%20Flows%20that%20are%20configured%20to%20run%20on%20changes%20to%20a%20SharePoint%20List%20item.%20Most%20of%20the%20time%20it%20works%2C%20but%20every%20now%20and%20again%2C%20Flow%20does%20not%20execute.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20compare%26nbsp%3Bthe%20version%20history%20on%20the%20SharePoint%20list%20item%20with%20the%20executed%20Flows%2C%20I%20can%20see%20that%20there%20is%20a%20missing%20Flow%20execution.%20This%20is%20causing%20a%20lot%20of%20issues%20as%20we%20cannot%20guarantee%20that%20every%20change%20will%20be%20processed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20changes%20are%20happening%20approximately%205%20minutes%20apart%20and%20the%20Flow%20usually%20take%205%20to%2020%20seconds%20to%20execute.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20see%20that%20the%20Flow%20user%20interface%20includes%20a%20view%20of%20%22Checks%20(no%20new%20data)%22.%20My%20only%20guess%20is%20that%20for%20some%20reason%2C%20it%20didn't%20detect%20any%20new%20data%2C%20even%20though%20the%20list%20item%20history%20shows%20that%20there%20was%20a%20change.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20others%20seen%20similar%20behavior%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-276078%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Flow%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1450958%22%20slang%3D%22en-US%22%3ERe%3A%20Flow%20not%20getting%20triggered%20on%20every%20change%20to%20SharePoint%20list%20items%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1450958%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3383%22%20target%3D%22_blank%22%3E%40Ivan%20Wilson%3C%2FA%3E%26nbsp%3Bdid%20you%20ever%20find%20anything%20out%20about%20this%20scenario%3F%20I%20see%20that%20this%20topic%20has%20been%20viewed%20over%20700%20times%20so%20my%20guess%20is%20others%20are%20experiencing%20it%20too.%20I%20have%20seen%20this%20occasionally%20as%20well%2C%20and%20am%20not%20sure%20what%20causes%20the%20Flow%20not%20to%20trigger.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

I'm experiencing issues with Flows that are configured to run on changes to a SharePoint List item. Most of the time it works, but every now and again, Flow does not execute. 

 

When I compare the version history on the SharePoint list item with the executed Flows, I can see that there is a missing Flow execution. This is causing a lot of issues as we cannot guarantee that every change will be processed.

 

The changes are happening approximately 5 minutes apart and the Flow usually take 5 to 20 seconds to execute. 

 

I see that the Flow user interface includes a view of "Checks (no new data)". My only guess is that for some reason, it didn't detect any new data, even though the list item history shows that there was a change. 

 

Have others seen similar behavior? 

1 Reply
Highlighted

@Ivan Wilson did you ever find anything out about this scenario? I see that this topic has been viewed over 700 times so my guess is others are experiencing it too. I have seen this occasionally as well, and am not sure what causes the Flow not to trigger.