Help for owners
Calendly booked me twice at the same time as my Google Calendar events
Short answer
Calendly only treats events marked busy, on the calendars you chose to check, as conflicts. A free event, an unchecked calendar, a lost calendar connection or a buffer on another event type can all let a clashing booking through. Check which calendars are selected and whether the connection is still active.
Does this sound like your situation?
- Someone booked a time when I already had a meeting in Google Calendar.
- Two people booked the same slot with me.
- It happens only with some event types or some team members.
- Calendly shows times that my calendar says are taken.
- It started after I changed accounts, calendars or passwords.
Why does this happen?
Only busy events on selected calendars block time
Calendly checks the calendars you picked under calendars to check for conflicts and blocks time during events marked busy. An event marked free, or one on a calendar that is not selected, does not block anything.
Confirmed by calendly.com
Calendly lost access to the calendar
Calendly's troubleshooting page lists a state where it has lost access to your calendar and cannot check for conflicts at all. A password change, a revoked permission or a reconnected account can cause it.
Confirmed by calendly.com
Free and busy rules allow overlaps
Calendly says it may still block times for its own events even when you mark them free in your calendar, and that free and busy rules can allow overlapping bookings. Behaviour differs between Calendly's own meetings and events from other sources.
Confirmed by calendly.com
New meetings go to one calendar only
Calendly adds new meetings only to the calendar chosen under calendar to add events to. If that calendar is not also checked for conflicts, or a team member looks at a different calendar, bookings appear to land on top of other things.
Confirmed by calendly.com
Buffers apply to each event type separately
Buffers are set per event type, apply only to new bookings, and in team events they can make round robin uneven or remove slots from collective events. Meetings booked before a change keep their old buffers.
Confirmed by calendly.com
What can I do about it today?
- Decide which booking to move and message that personContact the invitee yourself and offer another time. Do not cancel in a hurry if you are unsure which meeting is the more important one.
- Open the calendar settings in CalendlyLook at which calendars are ticked to check for conflicts and which one is set to receive new events. Include every calendar where you keep meetings.
- Check the connectionIf Calendly shows a problem with your Google Calendar connection, reconnect it from Calendly's calendar settings.
- Look at how the clashing event is markedIn Google Calendar, check that important events are set to busy, not free.
- Test with a second email addressBook a slot over a known busy event from the public page and see whether Calendly still offers it.
When should I bring someone in?
- Double bookings continue after the settings are correct.
- Several team members, round robin or collective events are involved.
- A custom website or app shows the times, and the times do not match Calendly.
How do I handle it?
- Reproduce one clashI take a real clash and list which calendar, which event type and which state of the event applied at that moment.
- Read the availability reasonsCalendly's own list of why a time is unavailable tells me which rule was or was not in play.
- Fix the configuration firstCalendars to check, calendar to add to, busy and free, buffers and booking limits are set so they agree with how you really work.
- Check custom code lastWhere a custom page or integration shows or books times through the Calendly API, I check that it asks for available times fresh rather than showing saved ones.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Does Calendly sync instantly with Google Calendar?
Calendly's connection article does not say how often it syncs, so I do not promise a timing. A short gap between a new event and a clash is possible.
Why did it work before?
Common triggers are a changed Google password, a reconnected account, a new calendar added, or an event type edited. Look for what changed on the date of the first clash.
Can I stop all double bookings?
Correct settings remove most clashes, but I cannot promise none, since another person can still create an event in your calendar between a booking being offered and being made.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.