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.
- 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.
- Here is the latest update from my Microsoft premier case:
"As per the details on the case, it seems that this is something a known issue where our internal teams are actively working on priority.
I am actively working with our internal teams to get an update on the same.
Please be rest assured, I am working internally and in discussion internally, Will keep you updated on the same shortly."
