Forum Discussion
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?
35 Replies
Hi all,
I'm having exactly the same problem.
Could you please help me?
- Engineers at Microsoft are working witha permanent fix for this error, one thing that can help to get around the problem could be to add a new user with a minimum 365 Basic license on the tenant and add it to the Administrator role on the calendar (Bookings administrator). Then make a new Connection with this user. It’s a workaround for us anyway...
Vignesh_KailasMicrosoft
Can you please raise a support ticket with the above information - With Client ID included?
Support request ID: 2209140040007587 opened.
- Will do, thanks.
