the drawbacks you listed are valid points, although I’m not sure about this one specifically. what sort of caching are you referring to? or is the drawback that you need to execute every step? If the latter, you can skip directly to the step you want to debug using the --include or --exclude flags, show here Command Line Runner | Drone
we could add a flag to the CLI that freezes the pipeline when a step fails and then drops you directly into the container with a command prompt. This would eliminate both concerns – you would not need to sleep and you would not need to know which yaml step fails ahead of time.