Flow Get Attachment now failing

[master_NK]

Hi.

I have 9 Flows that are all the same structure.

When new mail arrives > Get email, then Get Attachment and create that in Sharepoint.

All the flows have been working perfectly until Yesterday, Now the all fail at the GET ATTACHMENT action.

""error": {

    "code": "ErrorInvalidMailboxItemId",

    "message": "Item Id doesn't belong to the current mailbox."

  }"

Yet the GET email works with the same connector and that is working:

 FLOWError

[ChristianAbata]

@master_NK  please check the conection of both actions are the same.

[alrez]

Hi,

There seems to be some mismatch between where the email is arriving and where the get attachment action is trying to look. If you are triggering when a mail arrives in a shared mailbox, it might be trying to search your mailbox and isn't looking into the shared one. I would check the connections as per Christian's suggestions.

Regards,

Alex

-------

Community Support Team _ Alex Rezac
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[jamikulas]

I have the exact same issue.  Receive email, save attachments to SharePoint, record email in spreadsheet.  Everything worked great until yesterday.  Something had to have changed.

Now, my workflow is suspended, and I cannot figure out how to re-enabled it.

[DannyBoy2042]

 We are having same issue.  These flows worked for 9 months or more and now they are all broken.  I am seeing on the forums we are not the only ones.  Everyone getting "Item Id doesn't belong to the current mailbox".

[ChristianAbata]

hi @DannyBoy2042  @master_NK it seems that this is an issue and MS support team its working on it. I try to repply your error an yesterday get the same error but todays works find. Please try deleting your conections and rebuilt the flow.

[master_NK · Accepted solution]

SO i finally got mine fixed. Was using an account that was only a Exchange online licenses - changed the License to a Basic Business Licenses and redid the connectors and now all is working

[jeffchapmanjc]

Where can we see evidence of Microsoft working to resolve this so we'll know when it's fixed? 

[DannyBoy2042]

I have a support ticket in with them, they gave me a workaround to use MS Graph.  Not ideal but these were production flows and needed to work.  I was told that this is result of them removing some legacy flow triggers (When new mail arrives in a share mailbox).  Unfortunately i had 10 of these and had do a work around for them all using MS Graph. 

[jeffchapmanjc]

My 9 flows were working just fine - and mostly continue to do so, except for the last step in each where I'm using Mark as Read V2 for items within a shared mailbox. Microsoft must have changed how Flows work with shared mailboxes which broke this action. I'm trying Delete V2 next since I really don't need to keep copies of the emails once the flow has uploaded the attachments to SharePoint. Here's hoping!