I've noticed an issue with waitlist behavior.
An event had 10 spaces. One person (party of one) cancelled. There were three people on the waitlist, parties of 2, 3, & 4.
The calendar did not automatically move anyone into the space, presumably because there was no party of one to bump. BUT, the calendar also showed one available space on the front end. Is this the correct behavior? Because generally we would call the waitlisted parties to see if they wanted one space, rather than open the space back up to someone new. (This event was defiancelibrary.org/chimes)
Also, last week we had an event with 10 spaces (defiancelibrary.org/whimsy), and 2 parties of 1 cancelled, but nobody was automatically bumped at all, despite there being parties of 1 on the waitlist. The front end instead displayed 2 available spaces; none of the waitlisted parties were offered space.
- Jul 13,2026 AT 12:54PM - 1 hour agoMore info:
I created a new test event with a capacity of 10 (defiancelibrary.org/testing). I registered 10 attendees, then added two waitlisted registrations: Party A requested 3 spaces, and Party B requested 1 space. After canceling one registered attendee, the event showed 1 available space on the public calendar but did not promote Party B. I expected the system to skip Party A (which could not fit) and automatically promote Party B (which could). This is inconsistent with a separate test using a capacity-1 event (defiancelibrary.org/testing2), where the system correctly skipped an oversized waitlisted party and promoted the next party that fit.
(And if I hit ”sync count” on the capacity 10 event, that triggers the system to offer the available space to party B.)