Incorrect delta result from GetAsDeltaGetResponse on mail folder
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start with the Delta().GetAsDeltaGetResponse() and Delta().WithUrl(deltaLink).GetAsDeltaGetResponse() calls described in the reproduction, and trace how the returned items and delta links are handled. Reproduce the sequence of adding newer and then older messages to a mail folder. Done means each changed message appears once in the delta response with a usable new delta link.
Written by the indexing model from the issue text.
Description
Describe the bug
I am using Delta handling against a mail folder and have found that consistently if older messages are added to the folder the delta query will return them twice in the result
Expected behavior
Expectation is that the delta call would only return a message once
How to reproduce
Reproduction-
(dates of the emails added to highlight the problem, not specifically needed to reproduce)
Folder with 1 email (14/01/2026)
Client.Me().MailFolders().ByMailFolderId(folderId).Messages().Delta().GetAsDeltaGetResponse() against the folder
- returns 1 email plus the delta link for use later
move 2 more recent (20/01/2026 ) emails into the folder
Client.Me().MailFolders().ByMailFolderId(folderId).Messages().Delta().WithUrl(deltaLink).GetAsDeltaGetResponse()
- returns 2 emails and new delta link
move 2 older emails (09/01/2026, 22/12/2025) into the folder
Client.Me().MailFolders().ByMailFolderId(folderId).Messages().Delta().WithUrl(newdeltaLink).GetAsDeltaGetResponse()
- returns 4 emails (2x each of the emails it should be returning) and new delta link
SDK Version
v1.93.0
Latest version known to work for scenario above?
N/A
Known Workarounds
N/A
Debug output
No response
Configuration
No response
Other information
No response
- Dominant language
- Go
- Stars
- 335
- Forks
- 43
- Avg merge
- 6h 42m
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoftgraph/msgraph-sdk-go
-
ItemItemsItemPermanentDeleteRequestBuilderInternal.Post missing content body/content-type headersOpenstatus:waiting-for-triage type:bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
microsoftgraph/msgraph-sdk-go#980 ·
Maintainers usually reply within 1 day
-
status:waiting-for-triage type:bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoftgraph/msgraph-sdk-go#972 ·
Maintainers usually reply within 1 day
-
status:waiting-for-triage type:feature
Difficulty 3/5 1-2 days Newbie friendliness 45/100
microsoftgraph/msgraph-sdk-go#964 ·
Maintainers usually reply within 1 day
-
status:waiting-for-triage type:feature
Difficulty 5/5 Over a week Newbie friendliness 20/100
microsoftgraph/msgraph-sdk-go#940 · 1 comment ·
Maintainers usually reply within 1 day
-
status:waiting-for-triage type:feature
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoftgraph/msgraph-sdk-go#939 · 3 comments · 4 reactions ·
Maintainers usually reply within 1 day
All issues in microsoftgraph/msgraph-sdk-go
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
prime-radiant-inc/evener#4329 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
openwatersio/aiscast#277 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
restic/restic#22112 · 1 comment ·
Maintainers usually reply within 3 days