Reading Conflicts #
Before slots are rendered, MixCalendar fetches busy periods from every calendar you marked for conflict checking. Any candidate slot that overlaps a busy period, once buffers are added on both sides, is removed. Events marked free rather than busy are ignored, which lets you keep informational entries on your calendar without blocking bookings.
Writing Bookings #
Confirmed bookings are written to your destination calendar with the invitee as an attendee, the meeting link in the location field, and booking question answers in the description. Rescheduling moves the same calendar event rather than creating a second one, and cancelling removes it.
Update Latency #
Providers push change notifications, so a new event on your calendar usually affects availability within a minute. If a notification is missed, a scheduled reconciliation pass catches the difference. Slot data is also verified server-side at the moment of confirmation, so a stale page can never produce a double booking.
All-Day Events #
All-day events block the entire day only when marked busy. Many calendars create all-day entries as free by default, particularly birthdays and holiday subscriptions, which is why they do not block bookings unless you change their status.
Declined and Tentative #
Events you have declined are treated as free. Tentative events are treated as busy by default, and this behaviour can be inverted per connection under the connection’s advanced settings.
Privacy #
Only timing and busy status leave your calendar provider. Titles, attendees, and descriptions of your existing events are not stored by MixCalendar and never appear on a public booking page.
