Microsoft delta endpoint for OneDrive pagination broken (odata.nextLink remains the same, no odata.deltaLink) present.

Question

The delta endpoint pagination for one drive isn't working as expected.
The graph api documentation regarding delta endpoint states that "Your app should continue calling with the @odata.nextLink until you no longer see an @odata.nextLink returned, or you see a response with an empty set of changes. After you have finished receiving all the changes, you may apply them to your local state. To check for changes in the future, call delta again with the @odata.deltaLink from the previous response."

When I call the endpoint, I get the following response:

I then make the request to odata.nextLink and get the following response As you can see, the odata.nextLink field didn't change, when a new link should be in its place and the deltaLink field isn't found in the response. Repeatedly calling the odata.nextLink results in an infinite loop.

Answer 1

Hi @Dziak, Michal,

Thank you for posting in this community.

It is possible that the issue with the odata.nextLink field not changing in the Microsoft delta endpoint for OneDrive is due to processing delays.

According to the article, there can be varying delays between the time a resource instance changes and the time the tracked change is reflected in a delta query response. Sometimes, due to replication delays, the changes to the object might not show up immediately when you select the @odata.nextLink or the @odata.deltaLink. Retry the @odata.nextLink or @odata.deltaLink after some time to retrieve the latest changes.

Reference: Processing delays

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.