|
Michael
|
February 10, 2015 at 7:41 am
Hi, we had an event sell past its inventory last night. total tickets was 20 and we sold 24.
This happened once before, about two months ago.
In both cases, the event was created by Duplicating a prior event.
|
|
Michael
|
February 10, 2015 at 7:59 am
I’m wary of upgrading to 4.6.4 right now because I’m going on vacation tomorrow.
|
|
Sidney Harrell
|
February 10, 2015 at 12:07 pm
Was the selling out part, the last 5 tickets sold on the event, in an extremely short span of time? Because of the way apache spins up multiple threads to deal with a heavy load, it can cause concurrency problems for us. We are in intense development right now of a timer system, where the seat becomes reserved at the beginning of the process, but I cannot give a specific timeframe when that will be ready for release.
|
|
Michael
|
February 10, 2015 at 3:15 pm
That was my first thought, but no, in both cases they were not tight time frames. In the latest case they were hours apart.
not to sound superstitious, but I have a feeling it has to do with the way Tickets are handled when Duplicating an existing event to create a similar event.
|
|
Seth Shoultes
|
February 13, 2015 at 9:42 am
Hello,
Are you using PayPal as your primary method of payment? If so, sometimes there is a major delay between the time the customer pays and the time that it takes PayPal to report the payment. PayPal has had some major issues this past week or so and payment response times were in the range of several hours. So it may be a case of the customer paid, then PayPal updated the payment several hours later, and in the meantime, other people registered while for the seemingly open spaces, therefore causing the event to oversell.
We have a fix for this coming in the next day or so, that should help with this type of thing. Please keep an eye out for that.
|
