cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Advocate II
Advocate II

BadGateway (502) when forwarding an email to a shared mailbox

Hi,

A flow that has been running for several months is now failing with the BadGateway error:

- trigger='When a new email arrives in a shared mailbox'

- action='Forward an email' or 'Forward an email (V2)'

- status code=502

- Body=

{
"error": {
"code": 500,
"source": "flow-apim-msmanaged-na-centralus-01.azure-apim.net",
"clientRequestId": "7eef32fc-f78a-44e7-b5c9-3eeae8627a67",
"message": "BadGateway",
"innerError": {
"error": {
"code": "ErrorInternalServerError",
"message": "An internal server error occurred. The operation failed., Cannot open mailbox.",
"innerError": {
"request-id": "24a9e885-6755-4046-a563-29b1edf761ab",
"date": "2019-09-13T15:01:09"
}
The email is forwarded to another shared mailbox.
Thanks for helping me to fix this issue.
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

 

Hi @Erick ,

 

Thank for your reply!

It seems that re-creating the connection can slow down this situation, if it happens again, please let us know.

And according to the message provided by @shanemeisner , this seems to be by design, and it seems that someone has already stepped in.

 

Best Regards,

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

View solution in original post

4 REPLIES 4
Highlighted
Community Support
Community Support

 

Hi @Erick ,

 

Could you share the details of the Flow configuration and the Flow run history?

I did a similar test on my side, but I was unable to reproduce such an issue.

I noticed that the error code shows 500/502. This seems to be a temporary error. Please try to update the connection or recreate the connection and see if the issue still exists.

 

Best Regards,

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

We have an incident opened with Microsoft regrading this issue.

We have 15+ Flows that take attachements from Shared Mailboxes and place them in SharePoint Lists. Currently all of them are giving us the 502 error.

The response back we have so far is:

"Other actions might have worked with shared mailboxes till last week but now have started to fail, as the Office team have started shared mailbox migration and moving them to a different cluster. "

No ETA on a solution yet..

Highlighted

Hi Barry, Thanks for your reply. I did what you said (deleted and recreated all connections) and it is working since. I am only hoping the issue won't come back later. Here is the link on the flow: https://flow.microsoft.com/galleries/private/templates/5593c729da6a4ac7875c2db57ae5b136?utm_source=s... Let me know if you don't have access. Regarding the flow history I don't know how to export it. Is a screenshot enough? Thanks & Best Regards Eric
Highlighted

 

Hi @Erick ,

 

Thank for your reply!

It seems that re-creating the connection can slow down this situation, if it happens again, please let us know.

And according to the message provided by @shanemeisner , this seems to be by design, and it seems that someone has already stepped in.

 

Best Regards,

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

View solution in original post

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

Power Platform ISV Studio

Power Platform ISV Studio

ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.

Top Kudoed Authors
Users online (7,959)