So it turns out that the cause was indeed a rogue change they couldn't roll back as we had been speculating.

Weird that whatever this issue is didn't occur in their test environment before they deployed into Production. I wonder why that is.

you are viewing a single comment's thread
view the rest of the comments
[–] 11 points 2 years ago* (last edited 2 years ago) (1 child)

Change Manager who approved this is gonna be sweating bullets lol

"Let's take a look at the change request. Now, see here, this section for Contingencies and Rollback process? Why is it blank?"

  • source
  • hideshow 2 child comments