You’re offline. This is a read only version of the page.
I have two flows one which is a bulk update from SQL which updates a SharePoint list once a month and a second one which updates the SQL table when a user updates a record in the list.
The issue I have is when I do the bulk update the alternate flow is triggered and does a superfluous update back to the SQL table essential copying itself.
I tried disabling the second flow in the bulk flow and even added a 10-minute delay but as soon as I turn on the Update flow its starts copying back all the rows to SQL.
Whilst its not a huge issue it is a waste of resource and was hoping to stop the copy back
This is working as designed. Even if the flow is turned off, the triggers are queued up and will fire when the flow is turned on again. We've added a terminate right after the trigger step to clear out these queued items. Not idea, but not sure of another way. Good luck.
Hi @Sundeep_Malik ,
Thats an interesting approach, I will set up a dev area and give it a test and will let you know how it works for me
Thanks
Hey @tsql_simon
I have a solution for you but you cannot revert this setting back, so be really careful, I will suggest to try it on a test flow first then only make changes in the main flow.
So for this you will have to go to the setting of the trigger and open the option of concurrency and set it to 1.
By this setting, if one of your flow instance is running, the second flow instance will wait till the 1st doesn't finish.
But I am again saying this setting cannot be reverted back so please try it on a test flow first.
I hope this helps 🙂
#1
Michael E. Gernaey
497
Super User 2025 Season 2
#2
David_MA
436
Super User 2025 Season 2
#3
Riyaz_riz11
244
Super User 2025 Season 2
Share
Report
All responses (
Answers (
