Well, I'm just going to let it spin, go vote, then head in to work. If it goes through, great, if not, well it sucks to be me.
I would eventually like an explanation for why we got the "Oops" screen initially. The information presumably got there, so what caused the "problem processing your transaction"? The info was correct, so if it got there and got a response, it should have been processed. What exactly was the problem? If there were too many requests to process at once, it should have just queued them up, not rejected them.
SpinyNormani'm wiling to bet that it's all the people "attempting" more than once, essentially spamming Massdrop. some are saying they've attempted 20, 50, 100 times.
SpinyNormanI don't speak dev fluently, but sounds like there was a few issues.
1. Payment page got crushed by influx
2. The above destroyed the checkout database
3. The checkout database explosion seems to have rocked a few other things on the backend
4. Everything is on fire
edit: bot thing was a misunderstanding on my part. apologies.
AlexPkYou need to ban whoever used that bot. And what happens to a Paypal authorization that happened an hour ago and nothing appearing in the transactions page?
I would eventually like an explanation for why we got the "Oops" screen initially. The information presumably got there, so what caused the "problem processing your transaction"? The info was correct, so if it got there and got a response, it should have been processed. What exactly was the problem? If there were too many requests to process at once, it should have just queued them up, not rejected them.