4

I'm using Microsoft Graph API change subscription to handle created/updated/deleted calendar events.

I noticed that the API always sends at least one UPDATED notification for each newly CREATED event. A quick search shows that it's normal behavior.

My question is: can this be considered a guaranteed behavior of the API?

If so, my plan is to only subscribe to UPDATED and DELETED notifications and treat each UPDATED event as a potential CREATED event depending on if a local copy already exists. This approach helps me deal with concurrency issues. I just want to make sure I won't miss any CREATED events this way.

Improve this question
1
  • Yes i think you're good above. For more information refer the docs related to all the resources, how it works, calendarview etc . Commented Mar 20, 2021 at 4:25

1 Answer 1

Reset to default
1

Yes, it is a guaranteed behavior, it is a known issue when you use the change notification of the user calendar event(/users/{id}/events).

See Additional notifications for users:

Subscriptions to changes for user with changeType set to updated will also receive notifications of changeType: updated on user creation and user soft deletion.

Improve this answer
Sign up to request clarification or add additional context in comments.

3 Comments

Yes I saw that the documentation mentioned this for users, but not for events, so I just want to make sure.
@thankyoussd I think it also applies to this, /events is under the /users endpoint.
The link for Additional notifications for users doesn't appear to link to the issue anymore? Is this only resolved for user creation/soft deletion, but wasn't rolled out to other aspects like events? I am still seeing this behavior

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.