Non Available Times Showing up in Scheduler

Question and Answers
1

Every time I test around 3 pm MDT I get times for the evening of the same day even though its not the available times in my event configuration.

image
image786×711 38.6 KB

image
image657×666 27 KB

2

The times returned by the Nylas Scheduler API for availability are determined by the availability and availability_rules set in your Configuration object, including parameters like duration_minutes, interval_minutes, round_to, and the open hours in each participant’s availability.open_hours or in the default_open_hours. If you are consistently seeing evening slots returned when querying around 3 pm MDT, even though your Configuration specifies different available times, here are common areas to review:

  • Timezones: Ensure that both your Configuration and your availability queries specify the correct timezones (e.g., America/Denver for MDT) in the open_hours or default_open_hours fields.
  • API Query Parameters: The start_time and end_time parameters in the /v3/scheduling/availability endpoint must be in Unix timestamp (seconds) and represent the time window you want to check. If these are off (e.g., UTC vs. MDT confusion), you might get slots outside your intended range.
  • Configuration Object: Double-check your participants’ open_hours and the availability_rules in your Configuration to ensure they accurately reflect your intended availability.
  • Rounding & Intervals: The round_to and interval_minutes settings can affect when slots start and end. For example, if your slots round to the nearest 15 minutes and your intervals are not aligned with your open hours, slots may shift to unexpected times.

If after confirming these settings you still see unexpected availability, you may want to

3

Thanks for getting back to me. I did confirm everything is setup correctly on my end. I have noticed that if the requested start time or end time is after the open hours I have set, that is where it seems to bug. I confirmed this with the api as well. I think that is why I was seeing it around 3:30 pm each day. Since my meeting time is 60 min, interval is 15 min and my open hours end at 4:00 pm

4

@sam Any update on this? Is there a formal way to file a bug ticket? Thank you.

5

@sam I can confirm the issue and can reproduce this issue with @jonathan‘s instructions. If a request is made to the availability v3 endpoint and start time is set to after opening hours, it generates extra slots for the day of the start time timestamp. The slots for the subsequent days are returned as expected.

Can you please have a look?