Preview Tool

Cisco Bug: CSCvv99146 - Propagate recurrenceId for from O365/Google to Calendar API

Last Modified

Oct 07, 2020

Products (1)

  • Cisco Webex Teams

Known Affected Releases


Description (partial)

recurrent meetings are not shown in teams calendar

Meetings are identified by iCalUid+recurrenceId. This has always been the case for instances of recurring meetings.  Recently we have started sending recurrenceId to the CalendarAPI server for single meetings to handle meetings that are processed by attendee and where the user was invited to individual occurrences of a recurring meeting. The recurrenceId from the calendar store is what we need, rather than using the original start time or start date.
Customer's meeting that was processed by attendee (the organizer wasn't calendar-entitled) and the recurrenceId changes when the start time changes. Since we use recurrenceId to identify the meeting, it looks like a different meeting and therefore doesn't overwrite the meeting with the older start time.
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.