We were doing a deployment today at work where we excluded several steps from the deployment, but had to cancel and click “Try Again” for other reasons. When we had clicked “Try Again” and went to the deployment steps, the same steps were excluded as if it remembered the options from the first deployment attempt - yet when we did click “Deploy” it ran through all steps regardless.
Feels like the UI is remembering state that isn’t being applied on deployment time with “Try Again”.
Thanks for getting in touch! I’m very sorry you’re hitting this incorrect and annoying behavior. I’ve seen this reported previously, and I was able to reproduce this issue. The good news is it’s been fixed in version 2018.2.4, and you can reference the relevant issue here.
Would you be able/willing to upgrade to see if this fixes it for you?
Let me know how you go and if you have any further questions going forward.
