cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Emilio

Stopping flow from triggering themself

Submitted by Advocate I on ‎10-30-2017 02:11 AM

Referring to this post.

 

https://powerusers.microsoft.com/t5/Building-Flows/A-flow-trigger-itself/m-p/64473#M6005

 

Can you create a switch button that control the flow from triggering itself when the flow modifies the list it is working on.

 

Thank you 

Status: New
3 Comments (3 New)
Comments
hjaf
Advocate V
Advocate V
‎02-21-2018 10:39 AM

Any news or workaround?

Emilio
Advocate I
Advocate I
‎02-23-2018 12:29 AM

Right now the only possible workaround is to set up a condition that when the flow trigger itself it will exit the flow. I usally setup some hidden boolean column to manage that. 

The flow always run twice, but it works.

hjaf
Advocate V
Advocate V
‎03-08-2018 07:33 AM

I ended up making a FlowControl list, then I created a FlowControl-Flow that maintains tasks in this list to minimize the amount of flows watching the document library. This seems like a needless and ugly hack, but I have found no other solution.

 

What about flow management? perhaps 'update flow state' can disable itself when triggered and re-enable it (with run after all outcomes;) ? I have not been able to explore flow-management because it is in violation with my environments data-loss-policy for some reason, but his feels a bit like a hack as well. 

 

The triggers that monitor locations that it does work on will burn through free flow runs pretty quickly, not really a financial benefit to develop functionality to avoid that is there? 😕