Forum Discussion
Solved
Microsoft Bookings connector fails with "statusCode":502 BadGateway
Hi all good forces,
Has anyone any tips for this error, we have recently set ut a new Booking calender with new services but are not able to start the new trigger for Microsoft Bookings;
{"statusCode":502,"headers":{"Pragma":"no-cache","request-id":"..........","client-request-id":"..........","OData-Version":"4.0","Request-Context":"appId=cid-v1:...............","Access-Control-Expose-Headers":"Request-Context","Timing-Allow-Origin":"*","x-ms-apihub-cached-response":"true","x-ms-apihub-obo":"true","Cache-Control":"no-cache","Date":"Wed, 10 Aug 2022 09:32:02 GMT","X-AspNet-Version":"4.0.30319","X-Powered-By":"ASP.NET","Content-Length":"325","Content-Type":"application/json","Expires":"-1"},"body":{"error":{"code":502,"source":"flow-apim-europe-002-northeurope-01.azure-apim.net","clientRequestId":"........................","message":"BadGateway","innerError":{"error":{"code":"","message":"An error has occurred."}}}}}
Can you please raise a support ticket with the above information - With Client ID included?
- I'm still having the same problem. It works fine for only 1 calendar and only the the trigger "when an appointement is created". Problem for the 2 other trigger and for all my other bookings calendars.
Could you please help me?
Vignesh_KailasMicrosoft
LDeprit Please file a support ticket on us with the Trigger output. We will handle it on priority. This is not the same issue - most probably a different issue
Still having the same issue as OP here: BadGateway. Is the fix rolled out everywhere?
- They seemed to have fixed it now! On my side it's working at least!
- My flows suddenly started working too. After around 3 weeks of Bad Gateway Errors
- Vignesh_KailasFix for this particular Bad Gateway issue is rolling out now and most of the tenants are expected to see this soon. If we see more Bad Gateway issues please raise a support ticket with us as it will help us gather the right information. Thanks for trying this out and apologies for this bad experience!
- Mine last threw a Bad Gateway error 26 minutes ago - so doesnt seem to be for everyone. Did it just start working, or did you rebuild your flow?
- Recreated a new, didn't keep the old ones since I didn't have anything solid/working yet.
But didn't have like a working one with steps after that just stopped working all of a sudden.
- I have exactly the same problem. Anyone found a solution for this yet?
I noticed that it works for a new calendar but fails with an old one. Problem is, out 'old' calendar URL is widly spread already so don't like to remake....Anyone has an idea?- Oddly enough I created a new calendar to test this theory. the very FIRST time the flow ran, it gave me a different error - something about Staff members. So I adjusted rhe flow to try and resolve, and the very next time I got bad gateway. I think put the flow BACK to the original state -- Bad Gateway. Mind boggling.
- I'm deep into an MS Support case on this -- will report back if they provide any smoking guns on this one. So far -- iffy if that will happen.
- Did you get any response on your ticket? Microsoft support has been basically radio silence on the ticket I opened.
Hi everyone, I just deleted my bookings connector and created it again to resolve the problem as a workaround.
- Did anyone get a fix for this issue? I just started working with this connector this week and am still getting a 502.
- Vignesh_KailasCan you please raise a support ticket with us? This is the right way to get traction on this specific 502 issue.
Vignesh_Kailas Done, Case 2209140040004456 - thank you.
- I am having the same problem
- I'm also getting a 502 error when use both with Logic Apps and Power Automate. Anything I can do to resolve?
