How to respond to a failed load balanced service deployment

[stuvjordan-uroc]

What's the best procedure to follow when the deployment of a load balanced service turns out to have a bug that causes the containers run by the service to stop?

As best I can tell (...none of this is stated in the manual, right?), when I copilot svc deploy, and it turns out that the code I've deployed has a bug that causes containers the service runs to stop, copilot automatically tries many many (exactly how many? Does the documentation state this anywhere?) to redeploy the containers. (Why? At this point, I know they don't work. I just want the new deployment cancelled, and to look at the logs of the stopped containers to find the bug!)

My instinct in watching the (long!) process of many attempts to start new containers was that I should just ctrl-c to stop the process. But exactly what happens when I do that? Is that stated somewhere in the documentation? Makes me nervous to ctrl-c without having some reference saying exactly what effect that has!

Would someone spell out exactly what copilot does when newly-deployed containers stop and what my options are to intervene in or configure that process?