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; {"st...
Can you please raise a support ticket with the above information - With Client ID included?
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?
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.