Overbooking protection not working
Hey @Lucas Stefanski As a test client, logged into a browser window and account seperate form the one I log in as admin, I booked 4 seperate visits for April 14th and overbooking protection wasn’t triggered. The booking wer for the same service window, 8-10am, which is set to allow only 2 bookings. I tried it again for April 26th just now and had the same result. Ive included screenshots. I also noticed that when i click upcoming bookings as a test client, the results do not include the bookings i made 30+ minutes ago,, although the actual bookings page does show them (see screenshot).
Thanks, let me know if you have any questions.




Log in to comment and vote
Comments3
Lucas Steflor
Apr 21
Hey @Jackson PSPP , thanks for sending over the detailed screenshots. I’ll take a look. I know you’ve experienced issues with this in the past, so I definitely want to get to the bottom of it.
Jackson PSPP
Apr 23
Hey @Lucas Stefanski Here is some more info/an update update about the overbooking issue.
Yesterday, I saw that the 8 a.m.–10 a.m. service window on April 26 (the window and date i was able to overbook last week) was crossed out and showed no availability. Last i had check it was not blocked…
Seeing that the window was now blocked, I wanted to try booking three services again to see if overbooking was fixed. The service window i booked was 8-10am and the date was April 30.
Important: At some point, I reloaded the app in the pet parent portal as a test client to ensure I saw the correct number of active bookings on April 30.
When I went to book a third visit on the same day and service window, that window was crossed out, so I thought maybe overbooking was working.
I wanted to be sure so i tried booking 3 visits again, but this time it wasn’t crossed out and i could book 3
I realized that the one time it worked was after i had reloaded the page or app so I wanted to try that.
First i checked and it was still letting me overbook. That’s when i turned on screen recording ….
Let me know if you have questions, thanks for looking into this.
Lucas Steflor
Apr 23
Hey Jackson, this context really helps, and I think I've got a handle on what's going on now.
The short version: the system’s current enforcement of the limits occurs only at a single point in the booking flow. What this mainly translates to (among some other smaller issues) is a subpar handling of multiple clients booking at the same time. I believe you experienced a version of this when having multiple tabs open.
In day-to-day use with real clients, the likelihood of this surfacing is fairly low, and lower still the fewer clients you have. That said, it's something I want to fix properly rather than patch. Tightening up the enforcement will take a bit of restructuring under the hood, so I'll keep you posted as I work through it. And definitely let me know if you ever see this happen outside of a testing scenario.