# Cannot remove failed rack **URL:** \ **Category:** Rack (Version 2)\ **Created:** [October 3, 2019, 3:02pm UTC](https://community.convox.com/t/cannot-remove-failed-rack/619 "2019-10-03T15:02:32Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![andreas.nilsson](https://avatars.discourse-cdn.com/v4/letter/a/53a042/32.png) [@andreas.nilsson](https://community.convox.com/u/andreas.nilsson)\ **Post date:** [October 3, 2019, 3:02pm UTC](https://community.convox.com/t/cannot-remove-failed-rack/619/1 "2019-10-03T15:02:32Z")
I was experimenting with a specific rack setup which would be deployed into one of our existing AWS VPCs, and most likely made a mistake somewhere. When the rack was launched, it never managed to even attempt to launch and is instead stuck in a “spinning” state. I have no logs (using the console) since there is no rack yet and according to AWS there hasn’t even been an attempt at launching a CloudFormation stack. I also cannot delete the rack since it seems I can only do this once it is complete. The rack has been in this state for over a day now. This does not seem to be using any AWS resources, but I believe that if it hasn’t timed out yet, it never will. Has anyone been in a similar situation? Thanks! Andreas Nilsson ---
**Author:** ![jamie](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.convox.com/jamie/32/99_2.png) [@jamie](https://community.convox.com/u/jamie)\ **Post date:** [October 3, 2019, 4:05pm UTC](https://community.convox.com/t/cannot-remove-failed-rack/619/2 "2019-10-03T16:05:52Z")
It did take a good few hours for my rack to be built, but not a day. Also, I was using us-east-1 which is generally the slower, more saturated zone. ---
**Author:** ![andreas.nilsson](https://avatars.discourse-cdn.com/v4/letter/a/53a042/32.png) [@andreas.nilsson](https://community.convox.com/u/andreas.nilsson)\ **Post date:** [October 3, 2019, 10:29pm UTC](https://community.convox.com/t/cannot-remove-failed-rack/619/3 "2019-10-03T22:29:00Z")
The rack has now been spinning for a couple of days, so at this time it’s most likely a bug somewhere. At least this only seems to be on the Convox side of things, I see no AWS resources being commissioned. Gonna have to make it a support issue. Thanks for the reply!