Unable to update or delete shift-based schedules
This summary is created by Generative AI and may differ from the actual content.
Overview
On June 24, 2026, between 14:50 UTC and 19:25 UTC, a subset of PagerDuty customers in the US and EU regions encountered errors when trying to update or delete shift‑based schedules via the legacy Schedules API. The issue was introduced by a deployment that redirected calls to the newer API and was resolved by rolling back the change.
Impact
Customers were unable to update or delete shift‑based schedules; all other functionality—including event ingestion, incident notification delivery, schedule overrides, and web/mobile schedule management—remained fully operational.
Trigger
A deployment of a scheduling‑backend change intended to redirect legacy Schedules API callers to the newer API caused update and delete operations on legacy shift‑based schedules to fail.
Detection
The problem was identified after customers reported errors when attempting to modify shift‑based schedules, prompting the on‑call team to investigate.
Resolution
Engineers coordinated a rollback of the problematic change across the affected service regions, restoring normal operation at 19:25 UTC. A targeted fix preserving the intended redirection without the side effect was prepared for the next release.
Root Cause
The introduced change unintentionally broke update and delete functionality for legacy shift‑based schedules, making those API calls fail.