← Back to PagerDuty History
minor✓ Resolved

Issue Identified - Incident Workflows experiencing delays

PagerDuty•
Status
resolved
Duration
1h 18m
Updates
5
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
resolved
Summary On September 25, 2026, from 04:55 to 14:27 UTC in the EU service region, and from 12:36 to 14:32 UTC in the US service region, Incident Workflows containing a "Run JavaScript" action did not complete successfully. Affected workflows remained stuck at their "Run...
resolved
We have resolved an incident where customers in all Service Regions were experiencing issues with Incident Workflows. Impacted customers may have seen delays with a run Javascript action in Incident Workflows that could have caused delays with workflow related notifications. Event ingestion and...
investigating
We are monitoring improvement in an incident where PagerDuty customers in all Service Regions were experiencing issues with Incident Workflows. Impacted customers may have seen delays with a run Javascript action in Incident Workflows that could cause delays with workflow related notifications.</...
investigating
We continue to investigate an incident where PagerDuty customers in all Service Regions are experiencing issues with Incident Workflows. Impacted customers may see delays with a run Javascript action in Incident Workflows that can cause delays with workflow related notifications.  Event...
investigating
We are investigating an incident where PagerDuty customers in all Service Regions are experiencing issues with delays in Incident Workflows. Impacted customers may see delays with a run Javascript action in Incident Workflows. Event ingestion and incident notification delivery are not affected....

📊 TECHNICAL DETAILS

Internal ID
f5f2fb65-f62e-4c93-910a-581802ae7732
External ID
PC3716Q
🕐 Started
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
1h 18m
Total Duration
5
Status Updates
Affected Components
Incident Workflows (US)Incident Workflows (EU)
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed