Delays in applying schedule overrides
This summary is created by Generative AI and may differ from the actual content.
Overview
On June 5, 2026 at 18:00 UTC, a schedule override component in PagerDuty US region began experiencing lag due to elevated load, causing delays of up to 24 hours for schedule overrides and, after a backlog built up, up to 6 hours delays for Google Calendar conflict notifications. The issue was resolved on June 8, 2026 at 15:11 UTC after applying stricter rate limits, scaling the service, and modifying processing logic.
Impact
Subset of US customers experienced schedule override delays up to 24 hours and Google Calendar conflict notification delays up to 6 hours. Event ingestion, incident notification delivery, and web/mobile schedule management remained fully operational. No revenue impact reported.
Trigger
Elevated load on the schedule override component caused a processing bottleneck, leading to a backlog that eventually saturated downstream pipelines.
Detection
Customers reported delays; internal monitoring identified lag in schedule override processing, prompting investigation and on‑call escalation.
Resolution
Engineers applied stricter rate limits, scaled up the underlying service to increase throughput, and updated schedule processing logic to reduce lag, restoring normal operation by 15:11 UTC on June 8, 2026.
Root Cause
A processing bottleneck in the schedule override component under elevated load created a backlog that overflowed downstream pipelines, causing cascading delays for schedule overrides and downstream Google Calendar conflict notifications.