|
ARAGATO
|
October 16, 2019 at 10:51 pm
We have from time to time more than 1000 concurrent active users booking an event, because tickets are very very sought after.
Now, we have the issue that more tickets have been sold than the allow ticket count and the general limit of the related datetime (see screenshots).
https://i.imgur.com/4MF84F2.png
How is that possible?
The event has been correctly set to sold out and when I check now the ticket is correctly sold out. No more tickets are availbable to be bought.
When does the ticket count/limit check happens? At what step of the booking process? Could it be that just too many people literally simultanously clicked the buy button so that the system could ne respond in time with sold out and ticket not available?
|
|
Tony
|
October 28, 2019 at 6:04 am
Hi Aragato,
When does the ticket count/limit check happens?
The check is done when the user submits their tickets on the ticket selector, I’m fairly certain there’s another check during checkout but I can’t find it in the code so will double-check this with our developers.
When tickets are submitted it checks the current sold value + the reserved tickets against the number of available tickets. If there are spaces available the current selection is added to the reserved tickets for the duration of the session.
If high numbers of users are submitting tickets at the exact same time they could be submitting their values between the request from another user to verify and update the value. We’ve reduced that down as much as we but I guess with a high number of submissions all at the same time it could be possible.
If you view the TXN date timestamp for the registrations are they all similar values? That timestamp doesn’t necessarily need to be close to each registration as the session has a lifespan of 1 hour so after they’ve submitted some may take longer than others but it will give you a rough overview of how close the submissions were.
|
