Hello there!
My situation: I found the template "Book a new calendar event after a new SharePoint List item is created" and used it as reference. It uses the "When an item is created" trigger and works perfectly. I also used the "When an item is deleted" trigger and that one also worked. But when I use the "When an item is created or modified" trigger, it only runs when I start it twice.
e.g.
I have six items in my list. Then I modify one of them (change some values). After that the flow doesn't get triggered. But when I modify a second item in my list, for some strange reason, the first flow gets triggered and then the second one. It follows that pattern: First one doesn't trigger, second one triggers both.
I found several posts which are about the "created and modified" trigger, but no one wrote about what I experience. Any clues why it won't trigger the first time?
Hello NicoleHarris,
The issue described was not related to a timing thing. Waiting 5 minutes more did not triggering the worklow.
If we waited 10 minutes, 30 minutes or 1hour, the workflow did not start.
We had to edit something else (or the same item a second time) to trigger the workflow.
I think this may be a timing thing. I've found that this Flow isn't triggered immediately upon a item being updated/created, but rather that it takes up to 5 minutes (most of the time just a couple seconds to a minute) for the edit/creation to trigger the Flow. That seems to be by the design of Flow.
I am experiencing this same issue. Is there a corresponding item on the Reported Issues that I can upvote?
Same issue here with "When an item is created or modified" trigger.
Having the same issue. Will have to move my trigger from SharePoint "When an item is created or modified" to a PowerApps trigger.
Has something changed? Is there internal logic to prevent a "When an item is created or modified" infinite loop that is halting or aandoning triggers? Although I don't want to accidentlly create an infinite loop, I also want the triggers to fire correctly once the loop is handled in the code. Flow should either reject "...modified" flows that alter the trigger source, or allow looping and require devs to correct as needed.
Sadly I didn't find a real solution.
The only workaround I found was by replacing the original SharePoint editform with a customized one from PowerApps. In the app you can call your flow with your functions.
But as I said that's not a real solution. I don't want to use a customized app to edit my items.
I am encountering the same issue on a demo tenant.
In order to trigger a workflow on the event "created or modified", I have to edit two different items.
If I edit only the first one, I will wait several minutes without seeing anything happening from the Flow side.
Same issue here.
very annoying.
Hello,
I face exactly the same issue and it's quite annoying because I want to use this flow to create documents. Did you found a fix?
THank you,
Gabriel