Currently deployments can be canceled via the UI. However if the deployment is in the hung middle of a network operation the java process will wait for that to complete before clearing the hung deployment and allowing for more. It would be nice if this was handled more gracefully, ie. if x number of seconds passes without response from the deployment that we've tried to cancel remove it from the queue so it doesn't block other operations.

The only workaround now is to restart Bamboo and this is not an option in many high availability, high use environments.