Voice Notification contents Issue Identified
This summary is created by Generative AI and may differ from the actual content.
Overview
Between July 7, 2026 19:12 UTC and July 8, 2026 09:20 UTC PagerDuty customers in the US and EU regions received voice incident notifications that contained static variable names instead of the actual incident details. The issue stemmed from a library upgrade that omitted rebuilding translation files used for voice content generation. All other notification channels and platform components remained functional throughout the incident.
Impact
The degradation was limited to the content of voice notifications; customers could still receive, acknowledge, resolve, and escalate incidents via voice, and all other channels (email, SMS, push, Slack, WhatsApp) operated normally. No outage of PagerDuty services occurred, and there was no reported loss of functionality beyond the incorrect voice text.
Trigger
A library upgrade for the backend service that generates voice notification content was deployed without rebuilding the associated translation files. This omission caused the voice generation logic to fall back to static variable placeholders.
Detection
Customers reported hearing variable names in voice notifications, prompting PagerDuty on‑call responders to open a Major Incident at 06:28 UTC on July 8, 2026. Internal monitoring confirmed that only the voice content was affected.
Resolution
At 09:14 UTC on July 8, 2026 the affected code path was rolled back, restoring the correct translation files and voice content generation. The incident was declared fully resolved at 09:20 UTC.
Root Cause
The root cause was the failure to rebuild translation files after the library upgrade, resulting in voice notification generation using placeholder variable names instead of localized incident details.