Getting ` The selected timeslot is unavailable for participant` for all appointment booking requests

Question and Answers
1

With no change to code on our side, calls to POST /v3/scheduling/bookings have started failing 100% of the time with 400 invalid_request_error The selected timeslot is unavailable for participant errors. We used to get these occasionally for valid reasons (there really being no timeslot), but now we’re getting it 100% of the time for all requests, starting at ~11:46am PST today (2 hrs ago). Is there an ongoing outage?

2

@yashap thanks for posting, taking a look. Will circle back when I know more.

3

@yashap just taking a look, can you share a sample request payload?

4

Thanks for taking a look! Some example request ids from the error responses, if that helps:

  • Id1
  • Id2
  • Id3
5

A sample request payload:

{
  startTime: 1754607600,
  endTime: 1754611200,
  guest: {
    name: "Name",
    email: "Email",
  },
  participants: [
    {
      email: "email",
    },
  ],
}
6

Thanks @yashap - I just edited the posts to remove anything sensitive, but have taken it for reference.

7

Sounds good, thanks!

8

We did have someone reaching out to you guys through another channel as well, and from that channel it sounds like it may be a bug impacting round robin configurations, that’s currently being rolled back?

9

@yashap The team took a look and we do not see an issue on our end, continue with the separate channel so we can get more details.

Also, I modified the title :+1:

10

Sounds good, thanks for your help! As of ~5 minutes ago these errors stopped for us, so I’m guessing the rollback that Nylas team was doing completed :slight_smile:

1 Like