Answered

Get Emails (V3) failing when another uses it with error about shared mailboxes

(0) Share

Report

Posted on by DeanRoberts

My flow is called from Power Apps. The user is setup as a run-only user. The connection for the current user reflects his mailbox address. The same flow has SharePoint and Teams connections that work fine for the user. But Get Emails (V3) fails with the following message: "Your flow is failing.: As of May 6, 2020, shared mailbox support was added for certain operations with an optional 'Mailbox address' parameter, allowing you to specify a shared mailbox address for your operation to access. If you were using this operation prior to May 6, 2020, you will need to explicitly update your operations to specify the shared mailbox address. Please follow the Office 365 documentation for more information: https://docs.microsoft.com/en-us/connectors/office365/#shared-mailbox-support".

Is this a bug or is there something I'm missing?

Categories:

Using connectors

I have the same question (0)

All responses (3)

Answers (1)

Sort by

narayan225 2,547 Moderator on at

Like (0)

Report
Copy link

Link copied!

@DeanRoberts

You will need to check the Get Emails (V3) action to find the issue.

Check if the parameters you have specified are correct and if those parameters match the user's mailbox (the one thats running the flow).

If possible paste a screenshot (with sensitive information sanitised) in the thread so that we can troubleshoot more.

Cheers!

Was this reply helpful? Yes No
DeanRoberts 37 on at

Like (0)

Report
Copy link

Link copied!

See the attached images. I'm not passing any parameters except the search query which is filtering based on from and to addresses. I confirmed via a screen share that the user's Outlook connection was using his account instead of mine.

Looking at the output of the action, I see a status code of 404 and an error\code of ErrorInvalidMailboxItemId.

Here are the input parameters:

{"importance":"Any","fetchOnlyWithAttachment":false,"folderPath":"Id::****************************************","fetchOnlyUnread":false,"includeAttachments":false,"searchQuery":"(from:aaaaaaaaaaaaaaaaaaa OR from:bbbbbbbbbbbbbbbbbbbbbbb) AND (to:ccccccccccccccccccccccccc OR to:dddddddddddddddddddddddddd)","top":100}

and the resulting output

{"status":404,"message":"Item ***********************************' doesn't belong to the targeted mailbox **********************************.\r\nclientRequestId: **************************************\nserviceRequestId: *********************************,"error":{"message":"Item ********************************************************************** doesn't belong to the targeted mailbox *******************************************","code":"ErrorInvalidMailboxItemId","originalMessage":"Item *********************************************************** doesn't belong to the targeted mailbox ***********************************"},"source":"office365-wus.azconn-wus-001.p.azurewebsites.net"}

Was this reply helpful? Yes No
Verified answer

DeanRoberts 37 on at

Like (0)

Report
Copy link

Link copied!

This problem has been resolved. The Folder parameter for Get emails (V3) defaulted to Inbox. For some reason, it seems to have captured a cryptic id that pointed to the Inbox in my mailbox. I cleared out the Folder parameter and then removed it from the visible parameters. I confirmed in the code view that the folder was no longer present. Now it works.

Was this reply helpful? Yes No