A public booking page can open correctly and still have no eligible times. Cedros starts with the offering's saved weekly hours, then applies its booking window, duration, limits, time off, existing bookings, temporary holds, and connected-calendar busy time.
Start with the exact offering and the message invitees see. Work through the checks below in order, changing only a setting that is wrong for the schedule you intend to offer.
Identify what the page is telling you
- Select a day to see available times. Choose an available date in the calendar before expecting a list of times.
- No open times this month. Try the next month. Inspect the next month if navigation allows it. The current month may simply have no eligible slots left.
- No available times right now. The page did not find an open time while checking the permitted booking horizon. This does not identify which rule excluded the times.
- Could not load availability, or another displayed error. The lookup failed. Resolve the error before treating an empty calendar as a fully booked schedule.
- That time is no longer available. A displayed slot could not be reserved. Another booking or temporary hold, a changed rule, or a loading failure can make a previously displayed time unusable.
The page may initially move to a later month that has availability. Check the month heading as well as the selected date. Next month stops at the offering's future-booking limit; disabled navigation is not proof that the calendar is broken.
If you are an invitee, check the displayed timezone, try another permitted date, and contact the host with the exact message if the problem continues. The remaining setup checks are for the host or someone authorized to manage scheduling.
Check the exact offering and saved link
- Open Calendar → My calendar → Configure → Booking types.
- Find the offering the invitee is trying to book and copy its current booking link.
- Open that link in a private browser window. Confirm the host, offering title, and duration.
- Compare it with the link the invitee used, especially after a profile-handle or booking-type slug change.
A booking link includes both the profile handle and the offering's slug. A link to another type can show a different schedule even for the same host. Use the saved row's link instead of rebuilding it from memory.
If the page is missing or unavailable rather than showing an empty calendar, check whether the type still exists and whether the link changed. Weekly-hours changes cannot repair an obsolete link. See Setting up your public booking page.
Check weekly hours and timezones
Under Configure → About you, confirm the scheduling profile's Timezone. Under Availability → Weekly hours, check that the intended days are enabled and contain valid ranges. Each range must end after it starts, and ranges on the same day cannot overlap.
Weekly hours save automatically when a booking type exists. Wait for saving to finish, resolve any error, and reopen the settings to confirm persistence. If there is no booking type yet, hours entered in the panel are temporary until used in a saved type. Clearing every day closes the affected type's weekly schedule.
The current weekly-hours panel saves to the first booking type in the current list. Existing offerings can retain their own hours, so changing this panel does not establish that every offering now has the same schedule. On reload, the list is ordered by most recently updated type. Verify the exact public link after creating or editing an offering.
For comparison, set the public calendar's Time zone to the host's profile timezone. The public selector changes how slots are displayed; it does not change the host's working hours. Near midnight, the same slot can appear on a different date for an invitee elsewhere.
If the error mentions a local time that does not exist, check whether a weekly range crosses a daylight-saving clock change in the profile's timezone. Adjust the intended hours away from the skipped clock time and verify those dates specifically. See Setting your availability for weekly-hours and timezone setup.
Check notice, future window, and meeting length
Open the offering's Edit form and review Duration, then Advanced options → Booking window.
Minimum notice determines how soon a new booking can start. Check both the number and its unit: minutes, hours, or days. Two days of notice can remove today and tomorrow even when their weekly hours are open.
Future window determines how far ahead invitees can book. A date beyond it is unavailable until it comes into range. If the notice period extends beyond the future window, there may be no eligible dates at all. Read the summary below the controls.
The whole meeting must fit inside a weekly-hours range. For example, a 60-minute offering cannot fit into an opening from 10:00 to 10:30. A lunch gap splits the day into separate ranges; two short ranges do not combine into one longer appointment.
Times are also generated at the offering's configured slot spacing. A free interval does not necessarily produce every possible start minute. If a type has saved before/after buffers, those can exclude slots close to busy periods. The current editor does not expose every saved spacing or buffer value, so ask for help inspecting the type if those settings came from another setup path.
Save any intentional booking-type change with Save booking type before retesting. See Creating a booking type for these controls.
Check whether the offering has stopped accepting bookings
Under Advanced options → Limits, inspect Stop accepting bookings after and Total bookings limit.
Once the cutoff has passed, the offering stops accepting new bookings even if future weekly hours are open. Reaching the total limit also makes public availability empty.
The total limit is a cap across the booking type, not a daily allowance. Confirmed, attended, and no-show bookings count; cancelled bookings do not. Completing a meeting or marking attendance therefore does not reset the cap. A cancellation can free capacity, but cancel only when the meeting itself should be cancelled.
If the cutoff or cap was intentional, no setup repair is needed. If it is wrong, revise it deliberately and save the type. Raising a limit changes how many bookings you accept; it is not a refresh operation.
Check time off, bookings, and temporary holds
Under Availability → Time off, look for a block covering the intended period. Check its dates, recurrence, and Applies to scope. A block for All booking types affects every offering on the profile; a type-specific block affects its selected offering.
A recurring block may cover the date even if the row shows an earlier first occurrence. Time-off date inputs use the computer/browser's local timezone, while weekly hours use the profile timezone. Repeating blocks can shift locally across daylight-saving changes. Check the actual affected interval in the public calendar's timezone.
The upcoming time-off list currently loads the next 30 days. A block farther in the future may be absent after a reload without having been deleted. Do not create duplicate blocks or assume a missing row means there is no restriction.
Next, check My calendar → Bookings and the offering's Advanced options → Calendar conflicts:
- Respect my other booking types means bookings on other shared types can block overlapping times.
- Use a separate calendar allows this type to be tracked independently and can permit simultaneous bookings. It still respects applicable time off and Google busy time.
Do not select a separate calendar solely to make a slot appear unless you intend to accept overlapping meetings.
A visitor selecting a time creates a temporary reservation while completing the form. Another visitor, another browser tab, or your own earlier test can temporarily hold that slot. Wait a few minutes and refresh before diagnosing a lasting absence. Repeatedly selecting slots is not a read-only availability test and can create more holds.
Removing a block or cancelling a booking removes that restriction only. Other constraints may still exclude the same interval. For existing-meeting changes, see Managing bookings and schedule changes.
Check Google connection and booking readiness
Open Configure → Integrations if the profile uses Google Calendar.
When connected with sync enabled, busy periods on the configured Google calendar can remove slots. Check the displayed calendar identifier and compare an actual busy period in the same timezone. Do not assume every calendar visible in the Google account is included.
A Connected label describes stored connection state; it does not prove that the latest Google lookup succeeded. Resolve access, expired-authorization, or calendar errors when availability fails to load. See Connecting an external calendar.
Pause sync stops Google busy time from protecting availability. Do not use it as a shortcut to produce an open calendar unless you intentionally want that change in conflict checking.
Also distinguish availability from completing a booking:
- A Google Meet — automatic link offering requires the host's Google connection and enabled sync. Visible slots alone do not establish that the meeting can be booked or its link delivered.
- For a paid offering, Continue to payment starts a separate checkout step. A payment-setup or checkout error after selecting a time is not evidence that weekly hours are missing.
- A successful booking can exist while Google delivery or its confirmation email is still pending. Check the saved booking before submitting again.
Fix the reported readiness or delivery problem at its source rather than repeatedly changing hours or creating duplicate bookings.
Retest one change and collect useful evidence
- Confirm that the intended setting has saved, then reload the exact public booking link in a private window.
- Compare an expected open date with a known closed period, using the host's timezone first.
- Check the relevant future month within the booking window and repeat for other offerings affected by the change.
- Stop before selecting a time if you only need to inspect availability. A deliberate full booking test can create reservations, bookings, checkout, and notifications.
Availability displays are briefly cached and other visitors can book concurrently. Refresh after a saved change and read any current error; a screenshot of an earlier slot list is not a guarantee that the time can still be reserved.
If the result is still wrong, collect the exact public offering URL, the date and time you expected, the timezone shown, the visible message, and which settings you checked. Include whether the problem affects one type, one date, or every offering. A screenshot of the public calendar is useful; omit private management tokens, credentials, and unnecessary invitee details.
Use Getting help and reporting a problem for the support path. Keep the current booking and availability rules intact while the unexpected result is investigated.