I am proposing a new feature to CircleCI that allows us to set a step_max_duration to cancel an ongoing job. This feature would offer enhanced control compared to the existing no_output_timeout option by letting us determine a maximum duration for each step within the build.

Example use-case: if a step such as 'Checkout code' continues beyond a certain number of minutes, the job would be automatically cancelled.

I believe this feature would significantly improve CircleCI's flexibility, giving us the ability to more precisely manage our builds' time and resources.