How to Use the Calendar Troubleshooting Tool in PXME

Created by PX Marketing, Modified on Tue, 19 Aug at 3:00 PM by PX Marketing

Overview

The Calendar Troubleshooting Tool in PXME helps you test and refine your calendar setup before going live. It shows all potential time slots, identifies which ones are blocked, and explains why. This ensures your availability rules, buffers, and booking logic are working as expected—so clients have a seamless booking experience.


What the Troubleshooting Tool Does

  • View Slot Availability – See every possible slot based on your availability and intervals.

  • Hover for Explanations – Quickly identify why a slot is blocked (e.g., notice period not met, double booking, or resource unavailable).

  • Test Configurations – Adjust settings and instantly verify results without guesswork.

Example: If your availability is 10 AM–12 PM and 6 PM–8 PM with 60-minute intervals, only 10 AM, 11 AM, 6 PM, and 7 PM will appear. If Saturdays are unavailable, no slots will display for that day.


How to Access the Tool

  1. Go to Settings > Calendars.

  2. Select the calendar you want to test.

  3. Click Troubleshoot Calendar.

  4. The troubleshooting view will open, showing available and unavailable slots.


Key Features

1. Slot Availability

  • Displays all possible slots.

  • Hover over unavailable slots to see reasons such as:

    • Minimum scheduling notice not met

    • User unavailable

    • Blocked by another event

    • Outside defined availability

2. Multi-User Calendars

  • Collective Calendars: All assigned users must be free for a slot to open.

  • Round Robin Calendars: Availability adapts dynamically based on which users are available.

  • Hovering over a blocked slot shows how many users are unavailable.

3. Real-Time Adjustments

  • Update your calendar settings while troubleshooting.

  • Click Refresh to see changes applied instantly.


Codes & Their Meanings

The tool uses codes to explain blocked slots:

  • USER – No user available

  • COLLECTIVE – One or more users unavailable in collective booking

  • CONFLICT – Blocked by a third-party calendar event

  • BOOKED – Appointment already scheduled

  • BLOCKED – Manually blocked off time

  • NOTICE – Minimum scheduling notice not met

  • TOOFAR – Appointment too far into the future

  • DAYLIMIT – Daily appointment limit reached

  • SLOTMAX – Max bookings for that slot reached

  • BUFFER – Pre/post buffer blocking the slot

  • DURATION – Appointment length exceeds available time

  • PAST – Slot is in the past

  • LOOKBUSY – Hidden by “Look Busy” settings

  • NO SEATS – All seats filled for the event

  • RESOURCE – Required room or equipment unavailable


Benefits

  • Save Time – Eliminate trial and error with test bookings.

  • Ensure Accuracy – Confirm settings are working before clients book.

  • Support Teams – Ideal for testing collective or round robin setups.

  • Make Adjustments Instantly – Update and retest on the spot.


FAQs

Q1: What’s the purpose of the troubleshooting tool?
It shows which slots are open or blocked, and why, so you can refine your availability setup.

Q2: How do I access it?
Go to Settings > Calendars, choose your calendar, and click Troubleshoot Calendar.

Q3: Can I see why a slot is blocked?
Yes. Hovering over a slot displays the exact reason.

Q4: Does it work with all calendar types?
Yes. It supports Individual, Collective, and Round Robin calendars.

Q5: How does it handle Collective and Round Robin calendars?

  • Collective: All users must be available.

  • Round Robin: Availability adapts dynamically by user.

Q6: Can I update settings while using the tool?
Yes. Refresh after making changes to see updated results.

Q7: Can I test scheduling logic?
Yes. It’s perfect for testing rules like notice periods, buffers, and booking limits.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article