Hi everyone. I just want you to all know I'm aware of this issue. Unfortunately the ability to fix it is way beyond me since I don't know any programming. I've let the people that hopefully can troubleshoot it know before and I have again, but I want to assure you that it's not being ignored by me. I'm doing what I can 💔

Hello everyone! I'm really sorry about ignoring this topic, I thought (not anyones fault) that there was a staff response that we were still trying to get to the bottom of it.

I just pushed code that adds a 60 second timer between making CW purchases, and we'll monitor that change. I believe that this is some kind of race condition that comes from buying multiple CWs at a time, and something is stopping it from completing.

To be clear: we do track CW purchases (and could make a page for you to see all of your purchases, more on that soon!), but the code that runs when you make a CW purchase does a lot of things, and one of them is sending the event to you and logging it to our CW logs. The rest are sending the item, removing it from the shop, making sure the PW (if needed) is correct, etc, and I have been unsuccessful in finding where in that process the purchase is falling apart.

Another point - The code to put CSC into your account and send an event would be the same type of code that would put that CSC into a till and send you an event. The code we're using to log the information about the purchase would be the same code we'd use to create a user facing log where you can see all of the purchases. That isn't a solution to this issue.

This is a HUGE code image (sorry!) but it gives you an idea of how much goes on when you click the "buy" button. We have to check if you're using a voucher, we take the CSC, increase the number sold, give the item, make sure to figure out the profit correctly, send events to the releaser and the purchaser, log it to the users logs and our CW purchase logs (we log to two places!)

This is great code that I just don't have the tools to dig in to on new.subeta.net, and so it's been a game of adding logs to particular places in the code to see who gets to what spot and try to determine patterns, and so far all I've been able to determine is that it might be related to the purchase speed.

TLDR: Code has been pushed to add a 60 second timer between purchases, and we're monitoring now to see if that resolves the issue. If not, back to the drawing board!

I think (I'm not 100% sure) that it shouldn't be an issue, hopefully we'll see that born out!

I'm also going to see how hard it would be to rig up a page where you can see your purchases, since we do really log them, I promise! That's why it was frustrating for the UAs dealing with this in tickets (And y'all trying to write in about it) because the place they expected to see and confirm what you were saying wasn't reflecting that reality. Here is the first entry in the log in 2020!