Skip to content
This repository has been archived by the owner on Oct 11, 2024. It is now read-only.

fetch changes to emails even if the change is just [un]marking read flag #1866

Closed
Tracked by #1777
ashmrtn opened this issue Dec 19, 2022 · 0 comments · Fixed by #1867
Closed
Tracked by #1777

fetch changes to emails even if the change is just [un]marking read flag #1866

ashmrtn opened this issue Dec 19, 2022 · 0 comments · Fixed by #1867
Assignees

Comments

@ashmrtn
Copy link
Contributor

ashmrtn commented Dec 19, 2022

Updating the status of the isRead flag in M365 by marking an email as [un]read does not cause the item to be returned by the delta query unless the isRead field is specifically requested. This is likely due to the fact that changes to the isRead flag in M365 do not update the mod time of the item in M365

@ashmrtn ashmrtn self-assigned this Dec 19, 2022
aviator-app bot pushed a commit that referenced this issue Dec 19, 2022
## Description

Updating the isRead flag in M365 does not cause the mod time of the item to be updated. This means delta queries will not return items marked as [un]read when isRead is not one of the attributes requested in the $select clause.

Explicitly fetch isRead so that we get those items. Further changes will be required to ensure the mod time of the item is something that will not cause kopia-assisted dedupe to skip the item when only the isRead attribute has been changed.

## Does this PR need a docs update or release note?

- [ ] ✅ Yes, it's included
- [ ] 🕐 Yes, but in a later PR
- [x] ⛔ No 

## Type of change

<!--- Please check the type of change your PR introduces: --->
- [ ] 🌻 Feature
- [x] 🐛 Bugfix
- [ ] 🗺️ Documentation
- [ ] 🤖 Test
- [ ] 💻 CI/Deployment
- [ ] 🐹 Trivial/Minor

## Issue(s)

* closes #1866 

## Test Plan

<!-- How will this be tested prior to merging.-->
- [x] 💪 Manual
- [x] ⚡ Unit test
- [ ] 💚 E2E
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant