WSD – Exchange Calendar Reservation Synchronization and Status DiscrepanciesIssue Problem A meeting may display different reservation statuses in Microsoft Exchange/Outlook and ServiceNow Workplace Service Delivery (WSD). For example: A meeting appears as active in Exchange but is marked as Cancelled in WSD.A meeting is cancelled in Exchange, but the corresponding WSD reservation remains active.A room accepts a meeting invitation in Exchange, but the corresponding WSD reservation is marked as Conflicted or Cancelled. These inconsistencies can occur due to missed calendar synchronization notifications or reservation processing issues. Release All Cause There are two scenarios that can contribute to reservation status discrepancies. 1. Missed Exchange Cancellation Notifications WSD relies on real-time notifications from Exchange/Microsoft Graph to identify meeting cancellations. When a meeting is cancelled in Exchange, Exchange sends a deletion notification to WSD. WSD processes this notification and updates the corresponding reservation status to Cancelled. However, if the notification is missed or fails to process successfully, WSD does not automatically query Microsoft Graph to reconcile the current meeting status. Consequently, the reservation may remain active in WSD even though the meeting has already been cancelled in Exchange. This is a limitation of the current calendar synchronization architecture. 2. Reservation Availability Validation A known reservation processing defect, addressed by PRB2033088, can cause an incoming reservation accepted by an external room calendar to be incorrectly marked as Conflicted or Cancelled in WSD. The expected behaviour is that when an external room accepts an incoming meeting invitation, the corresponding WSD reservation should be Confirmed, even if another conflicting reservation exists in WSD. The external room booking takes precedence in this scenario. Resolution Steps to Resolve1. Upgrade all WSD plugins (Workplace Reservation Management and Workplace Calendar Synchronization) to the latest available versions to address the behavior. Ensure both plugins are upgraded to the same monthly release to avoid version-mismatch issues.2. Alternatively, deactivate the 'Validate Availability' business rule on the current version without loss of functionality.3. For existing inconsistent reservations, manual correction is required as there is no supported mechanism to resynchronize individual meetings using ICAL/CleanGlobalObjectId. Related Links PRB2033088