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.

  • No1@aussie.zone
    link
    fedilink
    arrow-up
    11
    ·
    edit-2
    8 months ago

    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?”