TimeTap incident
Issue Showing Availability for Service Profiles with Advanced Location-Specific Availability Configurations
Resolved after 3 hours 30 minutes, affecting Client Scheduler - US and Backoffice - US, on May 8, 2025.
A fix has been implemented and we are monitoring the results.
Affected components
Update timeline
- identified May 08, 2025, 03:41 PM UTC
We've identified an issue where services with Location-Specific Availability for Service settings (Time section of service profile) that are customized beyond the main Location selection (to also specify Days of the Week, Times, or Dates) are not showing availability correctly on Client Scheduler booking sites or in the Backoffice. This has been escalated to our dev team with top priority, and we'll share updates as soon as more info is available. Workaround: As a temporary workaround, you can remove any configured Days, Times, or Date ranges from the Location-Specific Availability settings, leaving only the main location selected. After saving this change, availability should display correctly for that service. However, once the issue is resolved, you’ll need to set up the your original Days, Times, and Date settings again.
- monitoring May 08, 2025, 06:48 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 08, 2025, 07:12 PM UTC
This incident has been resolved.
Your product runs on more than TimeTap
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.