This seems to be an expected behavior from EXO side, the similar latency can also be observed with EWS as well.
Also, the performance of the getSchedule depends on the no of participates passed in schedules
.
Hope this helps.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am using Microsoft Graph API endpoints /me/events to create appointments in Outlook calendar of attendees and /me/calendar/getSchedule endpoint to get free/busy schedule. First, I am creating an appointment with this endpoint /me/events, appointment gets created and is visible in Outlook calendar of Organizer and Attendees immediately but when I am calling endpoint /me/calendar/getSchedule to get free/busy schedule, that event is not returning newly created appointments. After 10 to 20 minutes when I hit again /me/calendar/getSchedule endpoint then the event is returning correct results. I have checked this on Microsoft Graph Explorer.
Example: 1. Create appointment for (test email) by calling me/events for 30mins(2022-11-05T03:00:00 - 2022-11-05T03:30:00).
2. Appointment created and able to see in outlook calender.
3. Immediately calling me/calender/getSchedule to get free/busy data but API(me/calender/getSchedule) not returning recently booked appointments.
4. After 10mins, when I hit it again me/calender/getSchedule returns booked appointments correctly.
This seems to be an expected behavior from EXO side, the similar latency can also be observed with EWS as well.
Also, the performance of the getSchedule depends on the no of participates passed in schedules
.
Hope this helps.
Hi,
Same issue observed by me while utilizing getSchedule API. Rarest scenario is 10 minutes of time to have it reflected. It is kind of intermittent, mostly within 2 - 10 seconds. Rarest cases above 10 seconds. That too on graph explorer.
Is there any justification do you guys have from MS? Kindly provide.