Hello,
I have scheduled a deployment to run every 15 minutes. However, there are instances where it may take longer to complete, which could potentially trigger the commencement of the subsequent deployment while the current one is still running.
To prevent overlapping executions, I would prefer either to have the upcoming deployment automatically cancel itself, or to have the subsequent deployments adjust their schedule to realign with the original 15-minute interval.
One solution I am considering is dedicating a worker pool to this deployment with a concurrency limit set to 1, assuming I've interpreted the documentation accurately.
Would this approach work, or is there a better alternative to ensure that only one deployment runs at a time?
Thank you for your assistance!
b
Bianca Hoch
11/02/2023, 1:46 PM
Hey Brian, yes, this approach should work!
Bianca Hoch
11/02/2023, 1:49 PM
> To prevent overlapping executions, I would prefer either to have the upcoming deployment automatically cancel itself, or to have the subsequent deployments adjust their schedule to realign with the original 15-minute interval.
I appreciate you mentioning your ideal case scenario, this pattern is something that our team is mulling over to see what UX enhancements can be made
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.