Posted: May 9, 2019 at 6:23 pm
Hi, my set up is as follows:
I have an event which has 20 tickets available. It shows 26 sold:
This is the only event out of 25 that has this issue.
When looking at the overall, the admin lists as 27 (not 26).
When filtering by Approved for this event, it also shows 27:
All events have a limit (varies). After the limit is reached, we are using the Wait List module.
How can more than available tickets be ‘sold’ (approved, Stipe & Invoice).
We have limited space for the events so this is a huge issue.
With the waitlist add-on, are you manually promoting users or are they automatically promoted?
Have users been promoted from waitlist to pending payment at all on the above event?
No, we have not utilized the plugin yet to manually promote users. We are at this state just collecting wait list registrants. The wait list module settings are the same for all events.
No, we have not used the wait list manager to promote anyone.
I look forward to your reply. Of all the issues we’ve had so far, this is probably the most important one due to limited space.
Hi again, it seems we have the issue with another event. This time Its not related to any 503 errors. Those were triggered by the number of people hitting the server, the ‘rush’ has passed.
This event has 36 sold, but the ticket only has 35 available and 35 tickets sold. This new registration happened today.
Hi, so we need to figure out the best way to address this issue. The event is oversold by 7 tickets (space is limited).
-We have turned off automatic promotion on the waitlist.
What we would like to do:
1- Take the last 7 people who registered and move them to the waiting list.
Can you let me know what steps we can take to achieve the above?
Also, the post above this one is a related issue but a different event. IF you dont mind addressing both on a follow up.
Thank you so much!!!
Ok, lets break this down some:
Ok, so you are using a ‘Default Registration Status’ of Approved on all events?
Each time a registration is Approved, that value is incremented.
Each time a registration is changed from being Approved to something else, that value is decremented.
So whilst that number should be accurate, it’s not a ‘live’ count as such in that it’s not querying the database to pull all of the registrations and then counting the returned values, its simply pulling that value from the DB.
That value is a ‘live’ count of ‘Approved’ registrations.
Meaning when you load the events page, it pulls any registrations that have a status of Approved on the event and counts the rows returned.
So this is the number of ‘Approved’ registrations on your event.
Note that clicking on the link will actually show you all of the registrations on the event, if you have some that are pending payment, they will show up on that table.
?? I’m not sure I follow this answer. You don’t show any of the promotion settings above.
The reason I asked if registration have been promoted is if you manually promote waitlist registrations to pending payment then ALL of those promoted registrations are able to pay, even if there was only a single ‘space’ available when you promoted them.
Your next answer clarified that though:
Ok, Thank you.
Whilst the problem may well be the same, jumping between different events is going to confuse things, so it’s better to work on a single event to narrow down the problem than work through any others that may have the same issue.
So, on the event with 27 approved registrations if you look at the time stamp for the registrations were they all within a relatively short amount of time or are they spread out?
This I’m going to need to do some digging into to see if it’s possible and will post shortly.
Yes, wether they pay thought stripe or use invoice, their status is automatically set to Approved.
All 27 registrations happened in a 18 minute span.
Thank you for checking into this.
I have a new issue and I will start a new thread.
Hmm, then you may have multiple registrations all starting the process at pretty much the exact same time.
Do you have a group of registrations all showing the same time within the ‘Reg Date’ field when viewing the registrations?
Looks like the waitlist auto promotion is based on the Reg ID ASC, meaning if space becomes available the ‘lowest’ ID of waitlist registrations will be the next one promoted.
I’ve requested some feedback to confirm this is the case before moving forward.
Another option is to manually promotion the registration(s) if a space becomes available, the admin can then select the correct registrant to promote.