Alex Rolley on 09 Feb, 2018 03:52 AM
Thanks for getting in touch!
What you are seeing in the result of how we configure a deployment by default. When you trigger a deployment we deploy to machines in parallel (up to our task cap which by default is 5), and any error in the deployment will prevent any remaining actions from occurring. So, to try and explain that a little better what is happening in your case is:
This is by design, however you can set this project to use Guided failure mode (which is in the settings of the project itself). What this will allow is that if a deployment does fail to a particular machine it will pause the deployment waiting for your interaction, and you can choose to continue to the remaining machines.
I hope that helps with understanding what is happening with your deployment, please let me know if there is anything else that I can help you with.