[#594] Any detail about error handling of conflicted booking calls?

API General
,
1

Migrated from Redmine #594 | Author: Dev Zeals
Status: Feedback | Priority: High, I’m very impatient | Created: 2020-10-15

I guess there is no locking mechanism to prevent multiple clients from booking the same time slot, instead just eventually the earliest one gets it, while the rest receive exceptions, am I getting it right?

If that’s the case, I’d like to know a bit more details about the error codes in advance, so I may get a clearer picture on their expected error handlers.

What I’ve found from the documentation so far is a single type of error with potentially different reasons, i.e., “Throws BadRequest error in case invalid data was provided with detailed errors per field”.

I suppose AccessDenied is not for this situation, and the returned array or object won’t provide error types, either. I could be mistaken, though.

2

Dmytro Bondarev wrote:

You will get BadRequest exception (400 status code) with clear message what happened.

3

Dev Zeals wrote:

Hi Dmitry,

Thank you for such a swift reply.

Yes, that is what I get from the documentation. What we would like to know is more about the actual messages, such that we can probably parse the message and decide the next moves accordingly.

4

Dmytro Bondarev wrote:

We do not have full list of error messages, because they can be generated dynamically. But in such case you will get error “Oooops, you are too late. Someone just booked this slot. Please choose another time and try again.”.

5

Dev Zeals wrote:

Cool, thank you for the information!