I have a bunch of scheduled flows at regular intervals. Is there anyway to control that the subsequent run is only triggered post the successful/failure (not running state) of the previous run. I don't want 2 jobs of the same task running in parallel.
k
Kevin Grismore
10/04/2023, 1:37 PM
You could deploy a flow to a work queue with a concurrency limit of 1, so if a flow is scheduled to start while it's already running, it'll wait for the current run to finish.
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.