Outlook connector (Create event) bad gateway status code 502

[dimi]

Dear

I have gone trough every post i found about a status code 502 & Bad gateway error (none of them was about outlook connector) but still went trough them and nothing helped me solved it, seems Microsoft Flow team does'n reply to the post, not saying the are not working on it, but no response is not a great way in my opinion, and i most of the time had a pretty good experience with the Flow/Power Apps community.

So, these are the links i went trough:

https://powerusers.microsoft.com/t5/Connecting-To-Data/502-bad-gateway-error/m-p/129833#M3061

https://powerusers.microsoft.com/t5/General-Flow-Discussion/502-bad-gateway/m-p/141795#M14767

https://powerusers.microsoft.com/t5/I-Found-A-Bug/502-Bad-Gateway-when-creating-Planner-Tasks/td-p/1...

My issue:

We have a PowerApp that communicates (read/write) to a SharePoint list, we have a Flow that runs on that list when an item is created or modified and handles a proces. At the end of this proces we create an event in a persons calendar using the outlook connector action. All our employees are using this app and it works fine except for 1 person, and only yesterday. It has executed well in the past. I try to re-run the flow (8 times) but the create event action still fails, while other runs after it are going perfectly fine so its not a connector issue.

Maybe this is relevant, the persons mailbox is in French while others are in Dutch or English, but again this persons mailbox has not changed, neither did anything change on the "Rights/Permissions" or anything else for that matter and it worked 2 days ago.

Here is the error:

{
  "error": {
    "code": 502,
    "source": "flow-apim-europe-001-francecentral-01.azure-apim.net",
    "clientRequestId": "453cf4d9-e466-4d59-86b5-111ba149eef1",
    "message": "BadGateway",
    "innerError": {
      "status": 502,
      "message": "Request failed. Try again later.\r\nclientRequestId: 453cf4d9-e466-4d59-86b5-111ba149eef1\r\nserviceRequestId: 22b9f61d-de20-45bf-b1e3-45f39ca9006d",
      "source": "office365-we.azconn-we.p.azurewebsites.net"
    }
  }
}

Headers:

Pragma
no-cache
x-ms-datasourceerror
True
x-ms-request-id
22b9f61d-de20-45bf-b1e3-45f39ca9006d
Strict-Transport-Security
max-age=31536000
X-Content-Type-Options
nosniff
X-Frame-Options
DENY
Timing-Allow-Origin
*
x-ms-apihub-cached-response
true
Cache-Control
no-cache
Date
Fri, 28 Sep 2018 06:40:26 GMT
Set-Cookie
ARRAffinity=59fce84ed840ff13733470e527d4d138afeb7dd6f97aa09a47d6bce8875b278b;Path=/;HttpOnly;Domain=office365-we.azconn-we.p.azurewebsites.net
X-AspNet-Version
4.0.30319
X-Powered-By
ASP.NET
Content-Length
487
Content-Type
application/json
Expires
-1

[v-yamao-msft · Accepted solution]

Hi @dimi,

Thanks for feedback.

I am afraid that there might be some updates in France Central. I will help confirm this issue on my side.

Besides, as a temporary workaround, please suggest your customer change the mailbox to English to see if it will work.

Best regards,

Mabel Mao

[dimi]

@v-yamao-msft, thank you for replying, awaiting your response i will change the mailbox and see if that solves it.

Will report back if it worked or not.

[dimi]

So, changing the mailbox language did the trick, however the user, being french, didn't want to stay in english (can't blame him for that) so we switched back and a day later, retrying the Flow proces, it works and still works as of today.

This is solved but i can't see the reason it didn't worked tough, it would be nice to find out why it stopped working so we can anticipate or just know whats happening

Kind regards

[Nebu4805]

Hello everybody,

since a a few days we has the same "bad gateway" error on our flows, which are running 3 years without problems.

I also try a simple flow to create a calender event on a shared calender, without success, always "bad gateway".

Changing mailbox language of shared calender account did not help.

Any tipps or hints, many thanks for any reply on this...

[Enigmatheatre]

I am also seeing this problem. Any suggestions on how to fix it? The App was working fine but now will not create an event without this error.