Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move email with static graph ID for email results in duplication of emails #1042

Open
tiborrr opened this issue Dec 20, 2024 · 2 comments
Open
Labels
area: API Support Focused on MS Graph API itself priority:p1 High priority/Major issue but not blocking or Big percentage of customers affected.Bug SLA <=7days

Comments

@tiborrr
Copy link

tiborrr commented Dec 20, 2024

Describe the bug

Using the move mail endpoint with immutable graph ids for mail creates duplicate mails

    headers = HeadersCollection()
    headers.add("Prefer", 'IdType="ImmutableId"')

was used to get the immutable graph id

  1. Place email in test inbox ("Invoice processor test inbox"):
    image

  2. Move email manually in OWA to another folder ("Invoice processor test cannot process")
    image

  3. Call the move email endpoint to move email to ("Invoice processor test done"):
    Email is moved out of inbox ("Invoice processor test inbox"):
    image
    Test emails moves to target folder ("Invoice processor test done")
    image
    Test email unexpectedly also stays in ("Invoice processor test cannot process")
    image

I now have a duplicate of the email. This should not happen if you call move on a email right? Is this intended behavior because of the use of immutable graph IDs or is this a bug?

Expected behavior

Email should be moved not duplicated

How to reproduce

See bug description

SDK Version

1.12.0

Latest version known to work for scenario above?

No response

Known Workarounds

Use non static graph ID

Debug output

No response

Configuration

Ubuntu 22.04

Other information

No response

@tiborrr tiborrr added status:waiting-for-triage An issue that is yet to be reviewed or assigned type:bug A broken experience labels Dec 20, 2024
@Ndiritu
Copy link
Contributor

Ndiritu commented Feb 4, 2025

@tiborrr thank you for reaching out.

Just to double-check, is this the request you are making with the SDK? https://learn.microsoft.com/en-us/graph/api/message-move?view=graph-rest-1.0&tabs=http

@Ndiritu Ndiritu added status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close and removed status:waiting-for-triage An issue that is yet to be reviewed or assigned labels Feb 4, 2025
@shemogumbe shemogumbe removed the status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close label Feb 4, 2025
@Ndiritu Ndiritu added status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close and removed type:bug A broken experience labels Feb 4, 2025
@shemogumbe shemogumbe added area: API Support Focused on MS Graph API itself priority:p1 High priority/Major issue but not blocking or Big percentage of customers affected.Bug SLA <=7days and removed status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close labels Feb 4, 2025
@tiborrr
Copy link
Author

tiborrr commented Feb 7, 2025

@Ndiritu yes that is indeed that API that I am using

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: API Support Focused on MS Graph API itself priority:p1 High priority/Major issue but not blocking or Big percentage of customers affected.Bug SLA <=7days
Projects
None yet
Development

No branches or pull requests

3 participants