Malfunction on Graph API on Update Events + GetSchedule

Maurice Lohse 0 Reputation points
2023-05-02T16:48:38.2666667+00:00

Unfortunately there is currently a malfunction in the "Microsoft Azure Graph API" (https://learn.microsoft.com/en-us/graph/use-the-api)

Error pattern: Room bookings can be edited via the Graph API, e.g. via PATCH 'https://graph.microsoft.com/v1.0/users/{id | userPrincipalName}/events/{id}', these changes e.g. to the subject of an event can be seen immediately in Outlook. If you continue to query 'https://graph.microsoft.com/v1.0/me/calendar/getSchedule', however, the old subject remains visible. Only when a change is made, e.g. via Outlook/Exchange, can the change be seen again via the Graph API.

Is there a poll to fetch new data from Exchange's Graph API, or is it just a bug? The behavior has been present for about 4-5 days. Before running for 3 years.

Microsoft Exchange Online
Microsoft Graph
Microsoft Graph
A Microsoft programmability model that exposes REST APIs and client libraries to access data on Microsoft 365 services.
12,520 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Ab-8756 805 Reputation points
    2023-05-03T17:12:53.8766667+00:00

    Hello Maurice Lohse,
    Thank you for your post.
    I have done some testing from my end too. I thought the issue could be related to propagation, issue but it's not.
    I was able to reproduce the issue from my end. I waited for 30 minutes after I made changes to the booking via Graph PATCH but the updated event info is not visible with 'https://graph.microsoft.com/v1.0/me/calendar/getSchedule' call. It shows old Subject.
    The issue must be related to a bug therefore, I would recommend you create a support ticket by tagging Microsoft Graph.
    Here is the link to open a ticket;- https://developer.microsoft.com/en-us/graph/support.

    Let me know, if that answers your question.
    Thanks


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.