Flow with trigger "When_an_event_is_added,_updated_or_deleted_(V3)" suddenly stopped working today

(1) Share

Report

Posted on by shdrew

I have two flows that have been running successfully for at least a couple of years now that has "When_an_event_is_added,_updated_or_deleted_(V3)" as its trigger... but the flow suddenly stopped working today. The Flow Checker says there's a problem; when I investigated, the run details read "Your Office 365 calendar doesn't support the on change trigger."

Is anyone else suddenly seeing the same problem with this V3 outlook calendar trigger?

Categories:

Using flows

Power Automate Desktop

General topics

I have the same question (0)

All responses (4)

Answers (0)

Sort by

NV-21030115-0 12 on at

Like (0)

Report
Copy link

Link copied!

Same issue here. Working fine for a year and broke. We have a lot of business processes dependent on this, hopefully it is fixed. Encourage everyone to open a ticket with Microsoft in hopes it will be addressed.

Was this reply helpful? Yes No
shdrew 10 on at

Like (0)

Report
Copy link

Link copied!

Can you tell me how exactly I open a ticket with Microsoft? I tried, but I think I went to the wrong place because it said only a business's administrators could submit support tickets.

Was this reply helpful? Yes No
BCBuizer 22,705 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,

This seems to be a duplicate topic from an earlier reported issue: When an event is added, updated or deleted - trigger mysteriously stopped working

I suggest to follow up in that topic to keep the discussion centralized.

Was this reply helpful? Yes No
Suggested answer

Haque 3,005 on at

Like (1)

Report
Copy link

Link copied!

Hi @shdrew

The error "Your Office 365 calendar doesn't support the on change trigger" is a known limitation and recent behavior change in the Office 365 Outlook connector. This trigger has become unreliable or unsupported for certain calendar types, especially shared calendars, resource calendars, room calendars, and Microsoft 365 Group calendars. The problem stems from backend changes in Microsoft Graph and Exchange that affect how calendar changes are detected and synced.

Many users have reported this issue recently(as BCBuizer has shared the thread), even though their flows were working fine for years without changes. Microsoft has not officially documented a full fix yet, but the recommended workaround is to replace the event-driven trigger with a scheduled recurrence flow that periodically polls the calendar using actions like "List events" or "Get calendar view of events (V3)" and then compares event states to detect additions, updates, or deletions.

If this issue persists and impacts critical automation, raising a support ticket with Microsoft through your admin center is advisable.

Was this reply helpful? Yes No