Skip to content

A Session or Resource Is Unavailable

Use this sequence when a time is missing or a reservation is rejected. Start with the smallest failing example: one offering, one service/ticket, one session, and a known requested quantity. Record the offering timezone and whether the customer selected a resource.

  1. Offering: confirm it is published and booking is enabled. Compare the generated offering page with any separate embedded form.
  2. Session: inspect the saved schedule and its preview. Check start/end time, recurrence finish, date selectors, and timezone.
  3. Option: confirm the intended ticket/service exists, is available, and permits the requested quantity.
  4. Assignment: check whether resources are required, auto-assigned, or chosen by the customer. Verify eligible resources and their scope.
  5. Resource: confirm it is active and its weekly hours cover the complete occupied period.
  6. Exceptions: review active blocking periods and any temporary capacity rules.
  7. Capacity: inspect existing reservations, including Pending bookings, and the selected option/resource capacity rule.
  8. Buffers: include preparation and cleanup time when comparing overlaps and working hours.
SymptomFirst comparison
Every time is missingSaved schedule, booking enabled, valid options
One provider is missingResource eligibility, active state, hours, exceptions
Time fails near opening/closingOccupied period including buffers
Quantity one works, quantity two failsService minimum/maximum, option count, and resource capacity rule
A cancelled test still seems to blockSaved cancellation result, relevant session, other reserving bookings
Time differs between pagesService-duration override, offering/resource timezone, and actual display context
A service shows the wrong end timeFree version, saved service duration, fallback session end, and whether buffers are being mistaken for visible service time
Weekday headings do not match datesFree version, WordPress Week Starts On, and the offering timezone

Change only the rule you have identified, save its containing form, and retest the same request in a private window. Then test an intentionally unavailable time to confirm the correction did not remove a needed restriction. Do not routinely use the manual-booking conflict override as a substitute for fixing public availability.

If the problem remains, collect the offering/session, requested quantity, assignment/capacity choices, relevant resource hours/exceptions, and redacted booking references. Share those with support alongside relevant diagnostics; omit customer details and private ICS URLs. Use the availability reference to interpret the rules.