Flow Execution Policy : Stop Instance

[Snify]

I would like to see a policy which turns a flow basically to a trigger. E.g. a flow is started by a trigger (or manually) and is currently running. When the same flow (and/or the same trigger condition is met) the currently running flow should be aborted/stopped and not execute another instance at all. Workarounds can be global vars to track flows. Alternatively an init (running) flow list can be useful as well. Thank you for reading

[Desmanto]

I still don't get what you mean. Do you mean to stop instances in the sense of multithreading flow? Just like the one mentioned here : viewtopic.php?f=4&t=7933

[Snify]

I mean, lets say I have a flow with two triggers. One triggers at 1pm and another trigger is set to 2pm. Both triggers share the same flow. At 1pm the flow does a continuous running task (e.g. a sound file will be played - hence the flow is active during this). At 2pm the same flow runs again (depending on your execution policy). I miss a feature which just stops the current flow if it still running after it gets executed again. I hope I could explain it better this time.

[Desmanto]

Doesn't the execution policy "Stop" should stop the first execution and run only the second execution then?