Hi, Is it not possible to skip a new scheduled flow run if a previous flow run of the same flow is still in progress? I am not able to find any solution to this problem. I currently have flow.serve() deployed somewhere with limit and tagging concurrency set to 1. Even then, the next flow goes into the running stage before the previous finish. More surprisingly, I also observed the newer one actually started executing and the older one kind of hung up in a running state.
Also if its helpful to know, deployment level concurrency limits are being considered for the roadmap right now. I’ll let the engineers know you’re a plus one
Taylor Curran
07/06/2024, 12:58 PM
also fyi tagging concurrency limits only works for tasks not flows or deployments.
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.