Hey @Kosta Krauth thanks for the request! I want to look at it a bit more. Today you can already do this via Bulk Actions on the queued runs list: multi-select the earlier queued runs, discard them, then confirm the one you want. So you're not blocked in the meantime. But your underlying point is the interesting part. When you confirm a specific queued run, the earlier queued runs on that stack are usually obsolete, so discarding them is often exactly what you'd want anyway. We'd like to explore making that behavior more automatic rather than a manual cleanup step, so confirming the run you care about just does the right thing with the rest. Can you give me a bit more context?
In what context do you need that feature?
How many runs typically pile up in the queue when this happens?
Would you expect this to be fully automatic behavior, or a one-click "confirm and discard the rest" option that keeps you in control?
Log in to comment and vote
Comments1
Natalia Gazda
Sep 25
Hey @Kosta Krauth thanks for the request! I want to look at it a bit more. Today you can already do this via Bulk Actions on the queued runs list: multi-select the earlier queued runs, discard them, then confirm the one you want. So you're not blocked in the meantime.
But your underlying point is the interesting part. When you confirm a specific queued run, the earlier queued runs on that stack are usually obsolete, so discarding them is often exactly what you'd want anyway. We'd like to explore making that behavior more automatic rather than a manual cleanup step, so confirming the run you care about just does the right thing with the rest. Can you give me a bit more context?
In what context do you need that feature?
How many runs typically pile up in the queue when this happens?
Would you expect this to be fully automatic behavior, or a one-click "confirm and discard the rest" option that keeps you in control?
Thanks!
Linked to Runs need a "Cancel all previous runs"