Resource event deltas
The Resource event deltas page lists calendar events the Exchange connector observed on a resource's mailbox but could not align with an existing appointment in Dime.Scheduler. Each row captures what was seen in Exchange so that administrators can decide whether the gap is expected, a sync timing artefact, or a real divergence that needs to be reconciled by hand.
Open it from the Exchange section of the navigation, or visit https://app.dimescheduler.com/resourceeventdeltas.
Layout
The page is split into two panes:
- Left - a list of resources that have one or more recorded deltas. Pick a resource to load its delta history. The splitter between the two panes can be dragged to widen either side.
- Right - the delta grid for the selected resource. Empty until a resource is selected.
Columns
| Column | Description |
|---|---|
| Start | Start date and time of the Exchange event. |
| End | End date and time of the Exchange event. |
| Delta | Raw description of what the connector observed, rendered in monospace so that timestamps and identifiers line up cleanly. |
All columns are filterable - text on Delta, dates on Start and End.
Actions
Each row has a delete button on the right. Removing a row clears that specific delta from the history; it has no effect on the underlying Exchange calendar.
When deltas appear
A delta is recorded when the bidirectional sync encounters a calendar event that does not correspond to a known Dime.Scheduler appointment for that resource. Common causes:
- The resource (or someone on their behalf) created an appointment directly in Outlook.
- An appointment was deleted in Dime.Scheduler while the matching Exchange event lingered.
- A sync ran during an in-flight change and observed a transient state.
Recurring or expected deltas - for example a personal calendar block that the resource keeps in their mailbox - can be left alone or removed in bulk from this page.
Related
- Two-way sync - how Dime.Scheduler and Exchange exchange calendar data.
- Exchange logs - the raw connector log stream.
- Transaction Errors - diagnosed appointment failures with
DSEXcodes.