Cant book meetings which are in the near future

[Neal0710]

Hey Guys,

on our website the cal.com does not allow clients to book something, does someone know why this could be ? Is there something we can do about. What is this error message

We have checked all the settings, and we cant solve the issue. Any help is appreciated

[dosubot[bot]]

Hi @Neal0710! I'm Dosu and I’m helping the cal.com team.

The "slot is no longer available" error is a known issue that has appeared in several Cal.com releases, often after updates to booking or slot availability logic. It can be triggered by bugs, temporary slot blocks, calendar sync issues, or configuration mismatches between the frontend and backend. For example, this happened in v5.0.19 and was fixed in later versions—sometimes a page refresh would temporarily resolve it, indicating a caching or state sync problem. Bugs like treating cancelled bookings as active, or not updating slot state after rescheduling, have also caused this error and were fixed in recent updates. Time zone misconfigurations, calendar service outages, or changes to availability settings (especially for team events) can also cause slots to appear available but not actually be bookable in the backend [source 1] [source 2] [source 3].

Here’s what you can try:

• Refresh the booking page and try again.
• Make sure you’re running the latest version of Cal.com, as several slot availability bugs have been fixed recently.
• Double-check your event type’s availability settings, including minimum/maximum notice, buffer times, and any date range or time zone restrictions.
• Review your calendar integrations—if Cal.com can’t sync with your calendar, it may block slots to prevent double bookings.
• If you use team events or managed event types, confirm that custom availability for team members hasn’t been reset to defaults after editing settings [source].

If the issue persists, check for errors in your browser console or server logs, and note any recent changes to your setup. If you can share your Cal.com version and any relevant logs, it’ll help narrow down the cause.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}