Why a booking or event was created even though you didn’t expect it
Sometimes a booking appears in your calendar that seems like it shouldn't have been possible—maybe you expected the time to be blocked, or another booking to prevent it.
On this page
Jump to any section using the links below
Sometimes a booking appears in your calendar that seems like it shouldn't have been possible—maybe you expected the time to be blocked, or another booking to prevent it. Here’s how to investigate and understand why the booking was accepted.
When to use this
You see a booking at a time that seems unavailable
You expected another event to prevent the slot
You're reviewing booking behavior for quality assurance or conflict checking
Key things to check
Was the time actually blocked?
Open the calendar and check for nearby events
Look closely at the event type: is it set to
BusyorFree?Only
Busyevents block availabilityFreeevents (like placeholders or reminders) do not prevent bookings
Check timing around the booking
Look at the order of events before and after the booking
Travel buffers and minimum gaps may still allow tight placements if settings are lenient
Was the booking made via a form or manually?
Click into the event
Scroll to the light gray footer text at the bottom (e.g.):
Booked Fri, Nov 21, 2025 14:02 using online booking
Click this to see full booking details, including form name and timestamp
Check which booking form was used
Different forms can have different rules (travel time, duration, address logic)
You can see the form name in the event details after clicking the gray footer link
Check for manual changes or edits
If an event was moved or edited manually after booking, it might explain the overlap
Open the lead history to see if the event has been changed
Edits to time, duration, or address can make a booking look unexpected in retrospect
Best practices
Always use
Busyfor calendar events that must block booking availabilityAlign settings across your booking forms to avoid gaps in protection
Use lead history and event footers to trace all changes transparently
If needed, temporarily disable a booking form while reviewing setup
Need help reading the event metadata?
Here's an example of the gray footer text to look for: Booked Fri, Nov 21, 2025 14:02 using online booking
Click it to view full source and logic behind the booking.
? Common searches
booking setup • calendar setup • appointment scheduling • booking configuration
? Also known as
appointment • scheduling • reservation • calendar event
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article