hmossessi, I understand your frustration (I have been in production for weeks now, I was the first person to identify the issue, and I was the first person to verify and try to escalate the issue), but if you consider the 30 minutes that it has taken Krileon to respond to the dead horse we've got lying in front of us, you might come to understand why they aren't as far along in the fix as you and I would both like them to be.
Please don't take this as an attack; I am frustrated, and I understand your frustration.
They've identified the issue, they've put it on the path where they think it is appropriate, and no amount of screaming "fire" is going to change it. So as a paying customer who is losing money while the coders attend to us rather than the code, please understand how it is important to me that you accept the answer you have and stop asking them to reconstruct the same answers over and over.
I'm sure they'd refund your money, as they would mine. And at this point this discussion is costing me money. Let's let them work, and just be mindful of what we cannot control.
Thank you,
S