Exchange logs
The Exchange logs page shows the raw log entries the Exchange connectorConnectorAn integration that links Dime.Scheduler to a back-office system, routing data in and scheduling decisions back out. emits while it processes calendar events, pushes appointmentsAppointmentA task scheduled to a resource for a specific period - the scheduled instance you see on the planning board., and reacts to Graph notifications. Use it to trace what the connector actually did when a sync misbehaves. It complements the Errors page: the Errors page shows diagnosed appointment failures with stable DSEX codes, while the Logs page shows the underlying log stream those diagnoses are drawn from.
Open it from the Exchange section of the navigation, or visit https://app.dimescheduler.com/exchangelogs.
Columns
| Column | Description |
|---|---|
| Date | Timestamp the entry was written. |
| Level | Severity badge. ERROR, FATAL, WARN, INFO, DEBUG, TRACE. |
| Category | The logical area that emitted the entry (sync direction, rule engine, Graph client, ...). |
| User | The user or service principal the operation ran under, when known. |
| Message | The log message. Hover the cell to see the full text without truncation. |
| Exception | The exception stack trace, when one was captured. Hidden by default - enable from the grid's column chooser. |
Filtering and sorting
Every column is sortable; most are filterable.
- Level offers a combo filter with the standard severities.
- Category, User, Message, and Exception offer free-text filters.
- Date supports a date filter.
Combine filters to narrow down to a single incident. For example, set Level = ERROR and Category containing Push to isolate failures while pushing appointments to Exchange.
The grid is paged. Use the pager controls at the bottom to step through history.
Export
The Export button in the toolbar saves the currently filtered view to an Excel (.xlsx) file. This is handy for attaching to a support ticket or sharing with a colleague who does not have access to the tenant.
How long logs are kept
Exchange logs are cleaned up automatically. A maintenance job runs once a day, shortly after midnight, and removes entries once they pass their retention window:
| Log level | Kept for |
|---|---|
| Error, Warning, Fatal | 30 days |
| Everything else | 7 days |
Failures are kept four times longer than routine chatter, because a problem reported at the end of the month is usually about something that happened weeks ago, while a successful sync from last Tuesday helps nobody.
The practical consequence is that this page is a diagnostic tool, not an audit trail. If you need a record of a sync beyond those windows, export it while it is still here.
Related
- Transaction Errors - diagnosed appointment failures with
DSEXcodes. - Troubleshooting - common Exchange integration issues.
- Resource event deltas - calendar events from Exchange that did not match an existing appointment.