Allow specific workflows to ignore auto-cancel redundant builds
N
Nick Bialostosky
There are situations where you would always want a workflow to run, even if a newer build has started. The current implementation of the "auto-cancel redundant builds" feature is all or nothing and doesn't allow granular control of which builds should be canceled. It would be great if the feature allowed for specifying workflows that it would ignore.
S
Sprunki Retake
I've run into this exact issue where certain critical workflows need to complete regardless of newer builds starting—having an option to exclude specific workflows from auto-cancel would be a game changer. It reminds me of playing Sprunki Retake , where timing and precision matter, and you can't just skip essential moves. Adding this granularity would really improve build reliability and developer peace of mind.
S
Sebastián Iglesias
It would be useful to at least have the option to allow different workflows to run at the same time, but only auto-cancel redundant builds.
b
branden@firebolt.io
There are two edge cases to the auto cancel redundant workflow setting that prevent my team from using this otherwise great feature:
- It doesn’t distinguish between multiple flows on the same commit. A developer couldn’t simultaneously run a workflowA and workflowB without workflowA getting cancelled.
- A new commit to a branch that had an active workflow caused the workflow to get cancelled. A 2nd workflow didn't even need to be started on the commit for the first flow to get cancelled.
Francis Upton IV
It would also be good if this were possible when using the API to submit a build.