Hi, when in my business tenant, when I try and use the Bookings connector I am adding the email address correctly from the URL on the booking link. All I have selected is "When a appointment is Created" and I have entered the correct SMTP address. Then I simply chose Compose for the next step just to be able to test this.
Issue is that no matter which account I use, I get the flow checker error stating
Details: It hasn't been triggered successfully in the last 28 days. This is the first day I have created it. I did read that when this connector was originally released it was a premium connector, but it is now a standard connector. All accounts I have tested with are and administrator for the Bookings calendar.
When I do this on my developer SharePoint tenant, it works as expected.
Solved! Go to Solution.
This was fixed by Microsoft this past weekend. The support case I had created they responded to saying they released an update to fix the connector and it did indeed fix it. I am now successfully running the booking connector.
Same issue. Any resolution?
I'm having the same issue. When I go to the trigger, the error details only state "BadGateway". I am the administrator of my bookings site and I'm the one creating the flow, they are both signed in using the same account. Any ideas?
That is the same for mine. Mine will only generate that error the first time a new flow is created with the booking connector. I have an existing ticket with Microsoft support, which is yet to be resolved. It has been pushed up to someone else 3 times now.
I was able to get this working by creating a new Bookings calendar. I could not get the Bookings connector to work with any of my old Bookings. It has worked perfectly with all new calendars I've created.
Interesting... that would be a nightmare for me to change to a new calendar. As I have had this ticket with Microsoft open now for almost 3 weeks, I plan to let them come back with hopefully a resolution, which I will update this posting with if/when that happens.
I just tried creating a new calendar to see if my issues continued, and I had a separate issue pop up saying {"ErrorMessage":"Staff not part of the booking mailbox."} . I'm still the administrator of the calendar and it's on the same account, so I'm not sure why I wouldn't be part of the mailbox.
What account is the flow set to run as?
Yes, suspect this is still due to the generated new Calendar having their own O365 tenant admin login and password (not the Bookings admin). Its that admin password needed for the connector. No idea who that was a practical useful process… Been dragging on now..
This was fixed by Microsoft this past weekend. The support case I had created they responded to saying they released an update to fix the connector and it did indeed fix it. I am now successfully running the booking connector.
After fix, getting different error
The user assigned on the trigger has to be setup as an administrator on the booking calendar. On the edit screen, click the 3 dots on the top right corner of the bookings trigger and validate the account shown is an administrator on the booking calendar.
Hello,
I am having the same issue with creating a flow from the action 'When an appointment is created'.
I am prompted with the following message, "There's a problem that needs to be fixed to trigger this flow. To see more details, open Flow checker." Once I upon flow checker, I get the message 'bad request'.
Where can I find the Bookings Calendar SMTP Address?
The smtp address is in the URL of the booking calendar. So when you open the booking page (where the user/customer would be filling out the form), it is shown on the URL.
Still not working for me. Same error. Checked account name is mine (Same account that made the Calander) and same user that is Admin the Bookings page. 🙄
Frustrating. Been waiting for this "fix" for months
Still think its something to do with the organisation tenant owner becoming a newly generated account ‘admin’ (without password) for every calendar that is created in Bookings.
Thank you, this worked
I'm also getting this error in my organization's environment. I've been working with the Microsoft Devs for a while now and still no fix. Friday, they emailed me saying that they were going to release a new fix and to try it again this weekend. Just ran my test with the same error.
Hopefully they will get this fixed.
I do believe I had to create a new flow for it to work. I am pretty sure it continued to fail on my previous flow created prior to their fix.
it fails