I'm having a lot of strange problems in my application and in my test environment, so I decided to back out my application and promote it again from the start. This would be in two parts. Part one, back out all update sets. Part two, promote and commit all the update sets in order.
I started backing out all the update sets starting with the most recent. Now I have only one update set, the first, remaining. So I clicked on Back Out on that one out too, and it chugged away for a long time, but the update set never went away. Now when I open the update set it displays a message saying
The Update Set Back Out button is unavailable because another operation is running: Back out update set <UPDATE_SET_NAME>
It's been about two hours. The Back Out button no longer appears, so I cannot try again. And I cannot say what state my application is in, so I cannot proceed to part two. Now what do I do?
Following up on this:
I deleted that row, but when I click on Back Out it just says Backing out XYZ: Job is not in the queue yet.
After a couple of hours and several more tries the Back Out dialog did go to 100%, but now it just sits there forever. There's no error in the log.
When I look at the list view the update set is still there, but interestingly the Application column is now (empty).
My goal is that, after further testing, I will re-commit this update set (and all the others, about 20 in all) for this application. But I appear to have an empty shell of update set #1 that won't go away. I'm not sure what to do next. Should I just delete this one and re-import it from the lower environment?
