Issue Identified with Saving Incident Workflows
This summary is created by Generative AI and may differ from the actual content.
Overview
Between July 14, 2026 13:42 UTC and July 15, 2026 13:41 UTC, PagerDuty customers in the US and EU service regions could not view saved Incident Type selections in the Incident Workflow UI. The selections were saved correctly in the backend, but the UI failed to render them. All other PagerDuty features, including event ingestion and incident notification delivery, remained fully operational.
Impact
The incident affected all PagerDuty customers in all service regions by preventing the display of newly saved Incident Type selections in the Incident Workflows UI for approximately 25 hours. Event ingestion and incident notification delivery were not impacted.
Trigger
A change deployed on July 14 2026 13:42 UTC that altered how the Incident Workflows UI parsed certain text‑based inputs unintentionally broke the rendering of multiple‑choice inputs such as Incident Types.
Detection
On‑call engineers began investigating after receiving customer reports on July 15 2026 11:28 UTC, confirming that the backend data was intact while the UI failed to display the saved selections.
Resolution
A targeted remediation was built, tested, and deployed to the affected production service regions, restoring correct display of Incident Type selections by 13:41 UTC. Additional actions include adding unit test coverage for the input‑parsing path and expanding test coverage in the automated UI testing suite.
Root Cause
The recent UI parsing change introduced a regression that stored saved Incident Type selections in a format the UI could not render, resulting in empty dropdown fields despite correct backend storage.