Skip to main content

On-call schedule with delayed alerts: how do I confirm the alert actually left PagerDuty during support-hours drift?

  • Nov 20, 2026 11:33 AM UTC
  • 0 replies
  • 3 views

 

 

I’ve been reading the thread 'On call schedule with delayed alerts’ (https://community.pagerduty.com/ask-a-product-question-2/on-call-schedule-with-delayed-alerts-1032) because we’ve hit something similar: alerts that look like they fired on time in the UI but clearly reached the phone much later, especially around our support-hours handoffs.

 

If it helps, I can also download the incident notification log and attach it here once I confirm which export gives the exact sent/received timestamps.

My question: what’s the cleanest way to prove whether the delay is on the PagerDuty side (notification/incident log) versus the downstream device? I’d like to compare the incident timeline, the notification log, and the on-call schedule change history for the same window before I start tweaking escalation policies. Is there a report or export I can pull for a specific incident to line these three views up, and does the mobile app cache notifications in a way that makes timestamps misleading?

 

If anyone has already chased this down with support, what evidence did they ask for first? I’d rather upload the right logs in one shot than go back and forth.

⌨

ETA --:--
 
⏸ PAUSE■ STOP