Microsoft Bookings connector
1 Topic
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."}}}}}Solved8.1KViews0likes35Comments