Iterating over delta tokens does not seem to be returning all driveItems, is it meant to?

[catmanjan]

Describe the bug

We have an established tenant with a decade of documents, if we iterate over all the delta tokens I was expecting to receive a notification of every driveItem ever made - but there seems to be some missing, including entire site libraries

Is this expected behaviour?

Expected behavior

I was expecting all the documents to appear

How to reproduce

A bit hard to do since you need an existing tenant with lots of activity, but basically just iterate over site and exhaust the driveItem delta tokens

SDK Version

No response

Latest version known to work for scenario above?

No response

Known Workarounds

No response

Debug output

Click to expand log

```

</details>


### Configuration

_No response_

### Other information

_No response_

[gavinbarron]

Are you trying to use a delta query to be able to get a list of changes ever, or just those looking forward?

These are intended to capture changes from when the initial delta query is made as a forward looking mechanism.

i.e. if I create a delta query for a document library that will return the current state of the library as it matches any extra OData parameters and then the deltatoken is used to fetch changes that occur subsequent to the inital call.

[catmanjan]

Yeah I was, where does it say it's meant to only support forward in time?

…

On Tue, 28 Oct 2025, 7:46 am Gavin Barron, ***@***.***> wrote: *gavinbarron* left a comment (microsoftgraph/msgraph-sdk-dotnet#2853) <#2853 (comment)> Are you trying to use a delta query to be able to get a list of changes ever, or just those looking forward? These are intended to capture changes from when the initial delta query is made as a forward looking mechanism. i.e. if I create a delta query for a document library that will return the current state of the library as it matches any extra OData parameters and then the deltatoken is used to fetch changes that occur subsequent to the inital call. — Reply to this email directly, view it on GitHub <#2853 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABBRBW2NU6SRX42YZBUK233Z2ABLAVCNFSM6AAAAABYX5LRU2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINJTGI2DAMBXGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>