Hi,
I see a lot of discussions around this item, but can't find the real answer online.
My issue is as follows:
- I have a sharepoint list
- I have a flow that should trigger on create or update of a list item in above sharepoint list
As soon as I create or update an item in the sharepoint list the flow is not triggered at all. As soon as I change the trigger to fire only on create, it works fine. What is wrong in my setup?
1) the settings of the flow-trigger
2) the flow
Solved! Go to Solution.
Hi @AG2019 ,
Thank you for the feedback!
Please keep an eye on this issue and let us know if this always happens.
Best Regards,
Ah , extra info. It's not triggering on the change on one specific field. This is a optionset (type is choice) field
Nevermind, somehow it's now triggering....
Hi @AG2019
Sometimes it might take sometime to trigger as well. The SharePoint triggers are all based on recurrence (which means they keep scanning for every 5 minute interval) so it might take until that much time for the flow to run (not that often though)
Hope this Helps!
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
Hi @AG2019 ,
Thank you for the feedback!
Please keep an eye on this issue and let us know if this always happens.
Best Regards,
I've been having this same issue again recently. It'll trigger inconsistently. The interesting part is that if I open the flow and save it (without making any changes), all the instances that didn't trigger will start immediately.
Hi yashag2255,
I know that there is some delay between implementing and effectuating, but in this case I was waiting for over 1 hour before I posted my question.
I have no idea what finally fixed the issue, but even now when it's working the reaction on a "on create" is much faster than "on create or update". Is this something you recognize or can explain?
Small test show an instance of my flow in 5 sec when the flow trigger "on create" and around 20 sec (sometimes more) when the flow trigger "on create or update".....
hello Ag209, a few days ago I started creating test the operation of flow and I ran into a similar problem but "when creating a file (Properties only)". I ask: can a stream have a trigger in addition to the original trigger? The stream I'm working on takes an attachment and classifies it into certain Teams private channel folders on sharepoint, according to keywords in the subject. My idea is that once a file is created in the sharepoint, a post is generated in the corresponding Teams channel, but the trigger does not activate and stops the flow, for many minutes, more than 30 or 40 inclusive.
User | Count |
---|---|
6 | |
6 | |
6 | |
4 | |
2 |