Skip to main content

Users on my company instance have noticed that PagerDuty is behaving differently when an incident is initially assigned to a team/service vs when a responder uses the “add responder” feature. Normally when an incident is ack-ed or resolved, further notifications are suspended or terminated. However, our major incident has begun engaging other teams by adding responders to existing incidents recently and it seems to work differently.

Users are reporting that they are getting notifications even after the incident has been resolved. Additionally, when there is more than one responder on a given escalation policy rule/level when one user acks the alert, that does not prevent other users from continuing to get notifications. Another difference is that the notification times and methods for each user contacted are not logged in the incident. This last bit was especially confusing for the users when we were first investigating this issue.

Is there a reason for this difference? It’s not intuitive for our users and is causing friction.

I found this section in the KB here: https://support.pagerduty.com/main/docs/add-responders

This tells me that this feature is not working as intended. Can we open a bug report for this issue?


Hi ​@Travis McGee, responder requests and incident assignment do not behave exactly the same, but this part does sound like a bug.

If you have an example of where this occurred, I recommend you raise a support ticket so the team can investigate.

When an EP is added to an incident, and a user on that EP accepts the responder request, the responder request should no longer escalate.


Reply