Issue with changing a meeting occurrence within a series in Outlook calendar

Hi,

Based on the behavior described, this issue can occur when Outlook or Exchange encounters a problem saving an exception within a recurring meeting series, or when the change to a specific occurrence conflicts with the existing recurrence pattern. Since the same behavior occurs in Outlook on the web, this suggests the issue is not limited to an Outlook profile or local cache problem. Instead, it may be related to the recurring meeting item itself within the mailbox.

Although Outlook does not provide a built-in option to identify a potentially corrupted occurrence, an Exchange Online or Microsoft 365 administrator can investigate further by reviewing Calendar Diagnostic Logs.

I recommend the following checks:

1/ Confirm the user is the meeting organizer:

Only the meeting organizer can make changes to an individual occurrence within a recurring meeting series.

If a delegate is attempting to make the modification, please also verify:

• The delegate has the appropriate permissions.
• Multiple delegates are not updating the same calendar simultaneously.
• The meeting is not being edited from multiple devices or clients at the same time.

2/ Check whether the time change conflicts with another occurrence:

In recurring meetings, Outlook may fail to save a change if moving one occurrence causes it to overlap with or bypass another occurrence in the same series.

For example, moving a Wednesday occurrence to Friday may cause issues if another occurrence already exists during that timeframe.

As a troubleshooting step, try moving the occurrence to a different time slot that does not overlap with any other occurrences in the series and then check whether the change can be saved successfully.

3/ Collect Calendar Diagnostic Logs:

I recommend asking an Exchange Online administrator to collect Calendar Diagnostic Logs for the affected meeting. The Get-CalendarDiagnosticObjectsSummary.ps1 script is the preferred method because it generates a clear timeline and Excel output, making it easier to analyze calendar-related events and identify meeting issues.

Whenever possible, collect the logs using the MeetingID, as this provides the most detailed results and can include information from multiple participants. Please note that Calendar Diagnostic Logs are retained for only 31 days, so it is best to collect them as soon as possible.

Example using the MeetingID:

.\Get-CalendarDiagnosticObjectsSummary.ps1 `
 -Identity "******@domain.com","******@domain.com","******@domain.com","******@domain.com" `
 -MeetingID "<meeting id>" `
 -TrackingLogs `
 -Exceptions `
 -ExportToExcel

If the MeetingID is unavailable, begin the investigation by searching with the meeting subject:

.\Get-CalendarDiagnosticObjectsSummary.ps1 `
 -Identity "******@domain.com" `
 -Subject "Meeting subject" `
 -ExportToExcel

Once the timeline workbook is generated, retrieve the MeetingID from the results and rerun the collection using the MeetingID for a more detailed analysis.

4/ Review recurring meeting exceptions:

For recurring meetings, the diagnostic script can also collect information about exception objects. To gather all exception dates associated with the meeting, run:

.\Get-CalendarDiagnosticObjectsSummary.ps1 `
 -Identity "******@domain.com" `
 -MeetingID "<meeting id>" `
 -AllExceptions `
 -ExportToExcel

The resulting timeline should help determine which occurrence was affected, as well as identify the client, delegate, or service that last modified or reverted the meeting.

If the logs indicate that the recurring series or a specific exception has become corrupted, the most practical resolution is typically one of the following:

• Delete or cancel only the affected occurrence and create a separate one-time meeting for that date.
• End the current recurring series before the problematic date and create a new recurring series for future meetings.
• Recreate the entire recurring series if it contains a large number of exceptions, as heavily modified recurring meetings are more prone to synchronization and exception-related issues.

In addition, I recommend confirming that the organizer and any delegates are not editing the same meeting from multiple clients or devices simultaneously, and ensuring that classic Outlook is fully up to date.

I hope these recommendations help identify the root cause and move the investigation forward. Should any further questions arise, please don’t hesitate to reach out again.

If the answer is helpful, please click "Yes" and kindly upvote it. If you have extra questions about this answer, please click "Comment".         

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.