Microsoft Bookings trigger can silently miss appointments
A Power Platform Community thread posted on 3 June 2026 reports a Microsoft Bookings flow that works once or twice, then stops triggering without run failures or broken connectors. Community replies point to a likely trigger-level issue, especially in one-to-many Bookings service setups, with scheduled polling via Microsoft Graph suggested as a workaround.
Before this kind of failure, a maker could reasonably assume that a healthy connection and clean run history meant the flow was working. That is the trap: trigger-level failures may leave no failed run to investigate because the flow never starts. For teams moving Bookings appointments into SharePoint lists, Teams notifications, or approval handoffs, this creates quiet data loss. The process looks automated, but the missing appointment only appears when someone notices the downstream record never arrived.
Analysis
Check any Bookings-triggered flows this week. Add a simple reconciliation check, such as a scheduled flow that compares recent Bookings appointments with the SharePoint list records that should have been created.
Pulse published by Collab365 Spaces. Cite as "Microsoft Bookings trigger can silently miss appointments", Collab365 Spaces. 1 source referenced.