I hear you, and I get you. but c'mon, this is the exact same bug that happened last time around.
Exactly the same thing. Were there no testers to test the exact same thing they knew could happen again?
I hear you. We're really frustrated too. We did test exactly this, shortly before shipping the release. And it worked properly when we tested it. Then it didn't work when pushed live. We're not sure yet how that happened, but we'll dig into it.