WSD Reservation sync going to "Error" after "Synchronization enqueued"
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
Hi Experts,
We are seeing an issue in WSD Reservation Management where the Synchronization State moves from "Synchronization enqueued" to "Error".
Earlier, this was likely due to users not being part of required AD groups, causing sync failure with Exchange. Now access is fixed, but existing records remain in error.
We are thinking of creating a UI Action to reset the state from Error → Synchronization enqueued to retry sync.
Questions:
- Is this a recommended approach?
- Will state change alone re-trigger sync, or are additional steps needed?
- Any risks like duplicate bookings or data inconsistency?
- Is there any OOTB way to retry failed syncs?
Thanks in advance!
0 REPLIES 0