DST 2026 Outlook Fix Guide
Outlook may preserve the meeting series while the real city-to-city overlap changes underneath it. The fix is to revalidate the pair, then republish the approved slot instead of trusting the old series.
If Outlook meetings started feeling wrong after a DST change, re-check the live city pair first, then update the series to the newly approved slot. The issue is usually offset drift, not the existence of the calendar invite itself.
Direct Answer
Most Outlook DST fixes are workflow fixes, not software tricks. Check the live city pair, approve the new best slot, and update the recurring series so the meeting matches the real overlap again.
The Four-Step Fix
- Confirm which city pair the meeting depends on.
- Check whether the current overlap is still acceptable.
- If not, choose the next best approved window.
- Update the Outlook series and republish the slot in UTC plus local city time.
Common Failure Pattern
| Symptom | Real cause | Fix |
|---|---|---|
| Same invite, worse attendance | Offset changed | Reapprove the slot |
| One region is always late now | Pair drifted at DST | Shift the series |
| Team keeps debating the time | No explicit timezone reference | Publish UTC and city times |
Related Pages
- Why DST breaks your recurring meetings and how to fix it
- Compare London to New York
- Compare London to Sydney
Frequently Asked Questions
Is this usually an Outlook bug?
No. It is usually a city-pair change that the calendar series did not force the team to review.
What should the updated invite include?
It should include the approved slot in UTC and the local city times people will actually follow.
When should a recurring Outlook series be reviewed again?
Before the next DST transition that affects the pair.