Staff Availability – MS Bookings Graph API call cache (probably)
Hello, I am facing a problem when checking staff availability for certain service before book an appointment.
It looks like the data received at the next request is out of date or possibly cached by the server:
graph.microsoft.com/v1.0/solutions/bookingBusinesses/{id}/getStaffAvailability
For example, if I book some appointment via the endpoint
“Cache-Control”: “no-cache, no-store”
to the query, but that didn’t work.
I would greatly appreciate any help or ideas on what I can do to get fresh data through the api, thanks.
Hello, I am facing a problem when checking staff availability for certain service before book an appointment. It looks like the data received at the next request is out of date or possibly cached by the server: graph.microsoft.com/v1.0/solutions/bookingBusinesses/{id}/getStaffAvailability For example, if I book some appointment via the endpoint/appointments I will immediately see the new booking in outlook.office.com/bookings/calendar, but at the same time, if I invoke a request to check the availability of the assigned person (/getStaffAvailability) I will not see this new appointment, the data will not be updated until a few minutes later. This leads to a double-booking problem for the same timeslot.A few pictures for a better understanding of what I’m talking about:I tried to set cache-control headers “Cache-Control”: “no-cache, no-store” to the query, but that didn’t work.I would greatly appreciate any help or ideas on what I can do to get fresh data through the api, thanks. Read More