Microsoft Bookings - When a appointment is Created not triggering

[llyrjones]

Hello,

I have a flow setup to trigger with MS Bookings - "When a appointment is Created".

It isn't triggering / running at all. I can confirm that I am an administrator on the booking calendar. I've deleted and created a new connection on the flow multiple times. Nothing is triggering it.

Any ideas?

Thanks

[creativeopinion]

@llyrjones Are you using the New Designer or Classic Designer? Try switching to the Classic Designer as the New Designer still has a few bugs. If that doesn't work, can you confirm your flow trigger connection? Click on the three dots of the flow trigger and check the connections listed at the bottom of the fly-out menu.

For more flow troubleshooting tips—check out this YT Tutorial: 5 Power Automate Troubleshooting FAQs and Helpful Tips for Creating Better Flows

In this tutorial I cover:

✅ How to troubleshoot a false Condition action result

✅ How to get dynamic content when it isn’t selectable from the list of dynamic content

✅ How to troubleshoot an Apply to Each action that isn’t looping through

✅ How to troubleshoot a skipped Apply to Each action

✅ How to troubleshoot a Filter Query

✅ How to use a SharePoint yes/no column in a Filter Query

✅ How to use Compose actions to troubleshoot a Power Automate flow

✅ How to troubleshoot multiple emails being sent

✅ How to troubleshoot multiple Teams messages being sent

Hope this helps!

If I helped you solve your problem—please mark my post as a solution ✅.
Consider giving me a 👍 if you liked my response! 

👉 Watch my tutorials on YouTube
👉 Tips and Tricks on TikTok

[llyrjones]

Hi @creativeopinion 

I have tried both designers.

The connection reference is also correct;

[creativeopinion]

@llyrjones Hmm that's so odd. Did you set any trigger conditions? Have you tried to create a brand new flow and just add a single action (such as a Compose action)?

[llyrjones]

@creativeopinion I've created a new flow, switched to the old designer and repeated what you've made in yours. Testing it now and nothing after making a booking, still not triggering.

[creativeopinion]

@llyrjones Confirming that you are using the same account to create the flow—that was used to create the booking page? I'm not saying that would solve your problem. I'm only asking cause that's how I set up my flow (with the same acct that I used to create the booking page).

[llyrjones]

@creativeopinion weirdly it's now started working with other users apart from myself. The trigger doesn't fire when I make a booking with my account (The same admin account) and when I run a test in the flow.

I'll keep and eye on it, and if it works for other users that book then that should be fine. Not sure if this is a bug or a feature of the API that if an admin makes a booking it doesn't trigger the flow. We'll see what happens.

Thanks for your help

[creativeopinion]

@llyrjones It does indicate the action is in preview currently. I'd imagine it's probably a bit buggy. Good luck!

[cipster]

Hi @llyrjones , I'm in the same boat, all connections are correct and the flow does not trigger. Tested on multiple test accounts.

[cimenta]

The same for me ... tried everything described above ...

[cipster]

Ok, I solved my issue. The bookings were made up of several slots hence whenever someone booked a slot nothing happened. When I used the updated action it worked like a charm.

[cimenta]

Great for you. I read your comment already on Friday and tried update connector instead of create and there was nothing in the run history. But I doublechecked now and I have one entry from today's testing.  Let me investigate.

Thank you so much for your last comment. It might save me hours of troublshooting.

[JenLavery]

I know there's a 5 month gap here, but I'm having the same exact issue.  I created the flow using a sys admin account (which is an administrator of the Bookings page), tested with my staff account and various test accounts, and nothing is triggering.  It's incredibly frustrating.

These are all one to one appointments.

The triggers for cancellations and updating work just fine, incidentally.

Did anybody manage to resolve?