cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
EGreen
Advocate I
Advocate I

Item Id doesn't belong to the current mailbox

Hopefully my final edit... @Anonymous alerted us that Microsoft has added a "Mailbox Address" field to Outlook actions. You can enter the address of the shared mailbox in this field to get back to original functionality. I'm keeping all previous solution details below just in case.

 

I've accepted the solution provided by @Anonymous on page 3. As a note for future users running into this issue, this solution requires a premium account. This will not be the best solution for a number of users (myself included), but it's the Microsoft-supported fix and (hopefully) the least likely to fail in the future. 

 

For more information on the Graph API solution, check the posts by @jonathanford on pages 5 and 6. 

 

If you do not have a premium account, the solution on page 3 offered by @Mindaugas is your best bet. You will need to add a new connection to Flow for the shared mailbox and then select that account as the connection for your Flow step. @RHCC gives more details on page 4 - you will also most likely need to add a password to the shared mailbox which is not intuitive. 

 

This is by far the easiest solution, but I'm concerned how long it will work before Microsoft breaks functionality in an update. They do not support shared mailbox connections in Flows that don't specifically use that language, which is a frustrating response given how many users were relying on these Flows for their daily business. 

 

Original post below:

 

Hi all - I'm having an issue with a couple Flows that were previously working without error.

 

When a new email arrives in a shared mailbox runs in a separate Flow and creates a SharePoint list item. One of the attributes added is the id of the trigger email (MessageId from the triggerBody). 

 

I have two other Flows that will reply to this initial email using Reply to email. The stored MessageId is used to reply to the correct email. This has been working for 4+ months without error, but started failing today with the error shown in the Subject (Item Id doesn't belong to the current mailbox). 

 

Myself and one other user are not having this failure. I had a user who was experiencing the failure check their connections in Flow and all apps were still connected. I also had them check their access to the shared inbox in Outlook and they still had full access.  

 

Has anyone run into something similar or have any suggestions? It seems like it must be a user connection to the shared inbox but I'm not sure what else to look into. Thanks!

 

**Editing to note that the Get email step is also failing when referencing the ID of an email in a shared mailbox.

2 ACCEPTED SOLUTIONS

Accepted Solutions
Anonymous
Not applicable

I found a "solution". Which is actually just doing what Microsoft is advising us to do: Use the Graph API.

 

First step is to use the HTTP with Azure AD connector: Invoke an HTTP request:

 

0.png

 

Then you have to create a new connection. In the documentation, Microsoft specifies that we must use "https://graph.microsoft.com/" as both the Base Resource URL and the Azure Resource URI:

 

1.png

Then simply click on "Sign In", and use your personal credentials.

 

Now you can simply refer to the Outlook REST API documentation (or the rest of Microsoft Graph).

Example on how to flag an e-mail:

 

2.png

 

Remember to change the shared mailbox in the URL: ENTERSHAREDMAILBOX@HERE.COM should of course be replaced with the shared mailbox that you are working with.

View solution in original post

Anonymous
Not applicable

My premier support tech just sent me the following message

 

I just wanted to provide you an update that after passing the feedback to the Product team that multiple users complained about existing functionality breaking,

The Product team has deployed a fix for this where an optional parameter is added to the outlook actions to specify the shared mailbox address.

This should provide the support and users should not see the error that they were seeing earlier.

screenshot.png

View solution in original post

146 REPLIES 146
rsaikrishna
Community Champion
Community Champion

@EGreen ,

Can you try removing the connection and adding it back? If the connection has any hickups, it will be corrected. Also, any changes to the a/c to the shared inbox will be refreshed.

 

Please let us know if this helps you.

@rsaikrishna  Thank you for the suggestion - I've had that solve issues in the past before. No such luck though, the Flow is still failing with the same error message. 

Anonymous
Not applicable

Has this issue got resolved? As i am also facing the same issue from yesterday.

I haven't found a solution yet.

 

@Anonymous Out of curiosity, is your issue also relating to a shared mailbox?

Anonymous
Not applicable

@EGreen Yes it is related to Shared mailbox

I am having the same issue.  I my flow is create an item in SharePoint from a shared mailbox, then delete the email.  The error is "Item Id doesn't belong to the current mailbox."

Anonymous
Not applicable

I'm having the same issue as well. My flow have been running for +2 months without any issues, now all are failing with the error:

"Item Id doesn't belong to the current mailbox.", when I am trying to "Flag E-mail"

Th same issue "Item Id doesn't belong to the current mailbox. on "Get Attachments" , did not any chnage and worked for 3 month

Just now I wrote ticket on MS support with this issue, so we will see...

Same issue - multiple failures on flow that monitors emails arriving into a Shared Mailbox.

@Stewartjohn100 Is the When a new email arrives in a shared mailbox trigger failing for you? Or a later flow that references the ID of the email in the shared mailbox? I haven't had any failures on the trigger so far.

 

@EmilBSP Thank you for submitting the ticket. Hopefully that will get some attention on this error.

I'm also seeing the issue.

 

The trigger works but when trying to save the attachment in the mail I get the error:

 

 
  "status"404,
  "message""Item Id doesn't belong to the current mailbox.\r\nclientRequestId: (AGUID)\r\nserviceRequestId: (AGUID)",
 
    "message""Item Id doesn't belong to the current mailbox.",
    "code""ErrorInvalidMailboxItemId",
    "originalMessage""Item Id doesn't belong to the current mailbox."
 
  "source""office365-eus2.azconn-eus2-01.p.azurewebsites.net"

Hi @EGreen 

 

My flow starts with "When a new email arrives in a shared mailbox" and then does some interim steps to capture data from the email and output it to a SharePoint. The final step in the flow is to Mark the email as 'Read'  (Mark as read or unread (V2)) - It's this final step that is failing - the error details are "Item Id doesn't belong to the current mailbox."

 

Thanks.

Error details:

 

{
  "error": {
    "code""ErrorInvalidMailboxItemId",
    "message""Item Id doesn't belong to the current mailbox.",
    "innerError": {
      "request-id""87da33ff-fa43-4cdf-8258-aa8cc6e23643",
      "date""2020-04-22T10:17:53"
    }
  }
}

UPDATE

 

It appears that the problem lies with the Action Get Email (V2)

If I create a basic flow using the trigger "When a new email arrives in a shared mailbox (v2)"

and use the action "Send a mail from a shared mailbox" to forward to my own mailbox - it works.

 

But if I try to do anything else with the email (copy the attachments via sftp in this case) using "Get email (v2)" I get the error - This only started happening today and the flow has been running for a long time.

timothydickson
Frequent Visitor

Indeed.  Same here.  Although my issue is intermittent.  It doesn't fail consistently... which is even more maddening.

Anonymous
Not applicable

I'm having the same issue. The Delete Email (V2) doesn't delete the email. The message id is being used.

I've started having the same error "Itme Id doesn't belong to current mailbox" since yesterday evening. This was working fine for a long time. 

jhargrov
Frequent Visitor

I am having the same issue this morning. I have 2 separate flows that get emails from 2 different Shared Inboxes and Create the email in a SharePoint list. Both are giving the error message below on the Get Email step. This has been working for almost 2 years without issue and just started last night. Need this fixed ASAP as it is holding up Business Critical operations. 

 

{
  "status"404,
  "message""Item Id doesn't belong to the current mailbox.\r\nclientRequestId: 6c40f5e1-81f3-4383-b667-c65ce0bbd6a7\r\nserviceRequestId: f940f2ba-16bd-45c0-bdc7-64fa427f3667",
  "error": {
    "message""Item Id doesn't belong to the current mailbox.",
    "code""ErrorInvalidMailboxItemId",
    "originalMessage""Item Id doesn't belong to the current mailbox."
  },
  "source""office365-eus2.azconn-eus2-01.p.azurewebsites.net"
}

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Results posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Solution Authors
Users online (4,128)