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.
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.
If you don’t test a restored backup, you don’t have a backup, same applies here.