|
Matt Shane
|
March 1, 2020 at 11:04 pm
Hello –
I have an event with a limit of 24 spaces and 5 waitlist spaces. The event shows sold out but the breakdown is 14 registrations, 9 reserved and 1 waitlist. What is the “reserved” column and how does it work. I guess I am confused how these numbers would add up to the 24 limit. Even if 14 are registered and 9 are reserved that equals 23 so why is there a spot waitlisted. Can you please explain and provide some direction. Thank you.
Matt
|
|
Tony
|
March 2, 2020 at 5:14 am
Hi Matt,
When a ticket selection is made EE places that selection in the reserved count for the duration of the session (by default 1 hour) to prevent overselling.
When sold + reserved tickets equal the limit set on the event, the event is sold out until a space becomes available (a reserved ticket is released to sale for example). Whilst the event is sold out it will show the waitlist button and the user can register so that will explain why you have a waitlist registration.
The event would likely have been showing sold out when the user loaded the event page, now a space has released and it shows 9 reserved.
|
|
Matt Shane
|
March 2, 2020 at 7:57 am
Hi Tony –
I am confused. So it sounds like the Reserved value is only temporary but those spots showed for days – not hours. Also, the numbers don’t match up. For example – the event shows SOLD OUT. I have 24 open spaces. 14 approved registrations, 1 waitlist, 9 under reserved and there are 15 transactions marked incomplete. I have the waitlist set to a limit of 5. So I am not sure how the system is assigning these values to each label and how to resolve. Hope that makes sense. Thanks! Appreciate your time.
|
|
Tony
|
March 2, 2020 at 8:48 am
I am confused. So it sounds like the Reserved value is only temporary but those spots showed for days – not hours.
That wasn’t in your opening post and changing things slightly as it can indicate a problem with WP Cron on the site.
Go to Tools -> Site health.
Wait on that page for at least 30 seconds (leave it open in another tab if preferred), does it show any issues with ‘loopback requests’ or ‘scheduled events’?
For example – the event shows SOLD OUT. I have 24 open spaces. 14 approved registrations, 1 waitlist, 9 under reserved and there are 15 transactions marked incomplete.
May I ask why don’t those numbers add up?
Limit = 24
14 Approved registrations.
24 – 14 = 10 spaces available without taking the reserved count into consideration.
9 reserved registrations, reserved + sold = total, so 14 + 9 = 23 leaving a single ticket.
As mentioned above, you may have had another reserved registration forcing the event to be sold out, that registration has now ‘released’ meaning it now shows 9.
I have the waitlist set to a limit of 5.
Just to confirm, have you seen how the waitlist system works when an event is sold out?
What happens is the ticket selector ‘Register’ button will switch to ‘Join Waitlist’ and it allows users to add their name and ticket selection on a modal.
Those registrations are saved with a status of waitlist.
So setting a waitlist limit of 5 to allow 5 registrations to do the above once the event switches to sold out.
For the above, list waitlist limit doesn’t actually come into it, so for now ignore that setting.
So in short, it sounds like your sold + reserved tickets were at the limit of 24 and another user added another registration, at that point, it is expected that registration would be a waitlist registration.
—
So I am not sure how the system is assigning these values to each label and how to resolve.
The ‘Sold’ value should be a count of all of the registrations with a status of approved on that ticket.
The ‘rsrvd’ count is the number of tickets EE currently considers to be ‘in session’, we can’t tell if the user is actively on checkout, so we hold the ticket for the duration of the session and then it should automatically be released.
(I understand that sounds like it isn’t happening on your site right now, but I want to make sure your clear on the above before digging into that more)
15 transactions marked incomplete
An incomplete transaction simply means the monies paid is less than the monies owed.
Note that is not the same thing as an incomplete registration.
|
|
Matt Shane
|
March 2, 2020 at 9:24 am
there is nothing under your plugin that relates to Tools -> Site Health
|
|
Matt Shane
|
March 2, 2020 at 9:33 am
I got it. you weren’t referring to your plugin. sorry
this is the error message from site health that looks like it is related to EE:
The scheduled event, AHEE__EE_Messages_Scheduler__generation, failed to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.
|
|
Matt Shane
|
March 2, 2020 at 9:33 am
there are no other errors
|
|
Tony
|
March 3, 2020 at 1:59 am
The scheduled event, AHEE__EE_Messages_Scheduler__generation, failed to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.
Can mean 2 things.
1. Your site is low traffic and the scheduled cron time for the above job passed without being triggered.
If that’s the case, it isn’t an issue as the next page load would have triggered it and removed that notice.
2. There is an issue with WP Cron (related to the above issue).
If you go to Event Espresso -> Messages -> Message activity.
Are all of your messages sitting with a grey status bar showing ‘Queued for generation’?
—
Go to Event Espresso -> Maintenence -> Reset/Delete Data.
Click the ‘Reset Ticket and Datetime Reserved Counts’ button only (others will cause you to lose data).
Now edit the event/refresh the event editor, does the count now look correct?
|
