By default command execution should be set to "always" | Feature Requests

By default command execution should be set to "always"

Mayank Shukla

Currently when we define any command then it only gets executed when the job passes. However, there are mostly chances where we want our command to be executed always no matter the job passed or failed. Can we have by default command execution set to "always"?

June 12, 2025

Keva Jolie

It is feasible to set up command deer adventure execution to always occur, irrespective of the job's result.

Gordon Bolton

Totally agree with this! It would make workflows much more intuitive, especially for cleanup or notification steps. Having "always" as the default would save time and reduce potential errors.

snow rider