Microsoft Bookings Trigger - Silent Failure

(2) Share

Report

Posted on by AdamH

580

Hi All,

I've tried to build a very simple flow that triggers when a new booking is made in Microsoft Bookings and enters the data into a SharePoint list.

Tigger: When a appointment is created

Action: Create item (SharePoint)

The issue I have, is that the flow just stops triggering. No registered failures, no broken connectors - It will work once or twice - then start to silently fail.

I've checked for limitations - I only have one flow for this booking mailbox and nothing else really jumps out as a problem.

Admin licence is E3 - so that will cover the usage

Anyone experienced this before?

Categories:

Building flows

Using flows

Using connectors

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

Haque 3,424 on at

Like (2)

Report
Copy link

Link copied!
Hi @AdamH,

I see two possible reasons:

1. Trigger Limitations and Delays: The "When an appointment is created" trigger may have internal delays or limitations in how frequently it polls or receives events from Bookings. Sometimes the trigger misses events if multiple bookings happen simultaneously.

2. Licensing and Quotas: Although E3 licenses cover standard usage, check your tenant’s Power Automate run quotas and limits to ensure you are not hitting any caps.

Possible troubleshooting:

Add Logging and Monitoring: Add logging steps early in your flow to confirm when it triggers and capture details. This helps identify if the trigger is firing but the flow is failing silently later.

Use a Scheduled Flow as Backup: Create a scheduled flow that periodically queries Bookings appointments via Microsoft Graph API or the Bookings connector to catch any missed appointments and create SharePoint items accordingly.

Note: You can monitor your flow’s run history for any hidden failures or throttling warnings. Also, verify your Power Automate quota usage in the Power Platform admin center.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
Suggested answer

11manish 2,938 on at

Like (1)

Report
Copy link

Link copied!
Given that:

The flow works initially.

No failures are logged.

Connectors appear healthy.

Licensing is sufficient (Microsoft 365 E3).

The problem occurs at the trigger level.

The most likely cause is a stale or failing Microsoft Bookings trigger subscription or a backend connector issue. Recreating the trigger and testing with a brand-

new flow are the best first steps. If the behavior persists across multiple test flows,

I would recommend opening a Microsoft support case, as this may indicate an issue with the Bookings connector service rather than your flow design.

Was this reply helpful? Yes No
Suggested answer

Valantis 6,371 on at

Like (2)

Report
Copy link

Link copied!

Hi @AdamH,

This is a confirmed known issue with the Microsoft Bookings Power Automate trigger. Microsoft Support has confirmed there are major issues with the trigger in 1:N (one-to-many) service configurations, with no ETA for a fix.

This is not your flow, your connection, or your licensing. Multiple users report the same silent failure pattern.

The only reliable workaround right now is a scheduled flow that polls Bookings via Microsoft Graph API instead of using the trigger. Set it to run every 5-10 minutes, query appointments created since the last run, and create your SharePoint items from there.

Alternatively, recreating the flow from scratch has resolved the issue for some users temporarily, though it tends to fail again after a while.
Raise a support ticket if you have access to one adding to the known issue report helps push Microsoft toward a fix.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
AdamH 580 on at

Like (1)

Report
Copy link

Link copied!

Hi All,

Thanks for your individual responses. I am using a 1:N setup for my services - so it seems that is where the problem more than likely is - if other users are reporting the same problem.

I won't have access to create a support ticket. I'll research how to use Graph to achieve what we need.

Was this reply helpful? Yes No