A powerful email and collaboration platform developed by Microsoft, designed to support enterprise-level communication and productivity. Miscellaneous topics that do not fit into specific categories.
Hi Dinesh,
Thank you for posting your question in the Microsoft Q&A forum.
I reviewed the behavior you described and found relevant guidance in the official Microsoft documentation here: https://learn.microsoft.com/en-us/graph/delta-query-overview#use-delta-query-to-track-changes-in-a-resource-collection.
The documentation states:
Based on this, the correct approach is to continue calling the @odata.nextLink until you receive the @odata.deltaLink, as you have already been doing. This is expected behavior and not an error.
While the documentation does not explicitly explain why an empty page occurs, here is a plausible hypothesis based on how delta queries work:
- Delta query, also called change tracking, enables applications to discover newly created, updated, or deleted entities without performing a full read of the target resource with every request. Microsoft Graph applications can use delta query to efficiently synchronize changes with a local data store. During paging, some items may have been deleted or moved after the initial snapshot, leaving a page with no items but still requiring continuation to complete the session. The
@odata.nextLinkensures you retrieve all remaining changes before the final@odata.deltaLinkis issued.
I hope the information above helpful.
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.