Recently active topics

Hey Community.  We held our Toronto PagerDuty User Group yesterday and wow, what a great turnout and great topics we had. We had a zoom conference running but to be honest, we didn’t have any one really join via zoom, which is probably a good thing.  These user groups should be done in person. What are your thoughts on PagerDuty User Groups? Do you want one in your city/region?  Do you agree it should be in person?  

Does anyone know why am i Getting this error while running a workflow,Message: Incident Workflow EV Testing completed with an error: Step "Send POST Request" did not complete successfully: Action has not been enabled for account

October’s extra special around here—spooky season meets our H2 Launch! That means treats, not tricks: we just shipped a massive wave of improvements across the platform! Check what’s new in PagerDuty and come back to let us know:

Hi,As part of a service orchestration rule or another type of rule, is it possible to check for the existence of an active incident within another PagerDuty service as a pre-processing step to paging us outBasically we have 2 PagerDuty services, App A and App B. When we get an incident in for App A, we’d like to check to see if there’s an active incident for App B that was created around the same time. If there is an active incident, then the escalation policy/notification policy gets enacted and people are paged out. Is something like that possible, assuming we have access to both of the PagerDuty services?

If you Awknowledge or Resolve an incident the Slackbot adds PagerDuty Username @slack-name to the Slack notification, but why tag me, the PD username I get? It seems very noisy and distracting If I’ve closed an incident I don’t need a Slack mention telling me so, I know I’ve done so, and everyone else can tell who it was by the PagerDuty Username

The PagerDuty MCP server now delivers deeper incident triage and event orchestration details via newly added APIs, enabling AI assistants and agents to access key PagerDuty data including outlier incidents, past incidents, related incidents, and service/global event orchestration configurations.   View the full session 👈🏾 Resources:- MCP API Documentation: https://developer.pagerduty.com/api-reference/d71edf8527b5e-pager-duty-mcp-api- GitHub Repository: https://github.com/mcp- GitHub MCP Registry: https://github.com/mcp 

I am configuring a new PD service where “Outside support hours” is set to “Dynamic notifications based on alert severity”. If severity is “high” the on-call engineer gets paged, otherwise it will be considered as low urgency. Up to this point all good. However, I want the alert to be raised to high urgency once we enter support hours. This is possible when “Outside of support hours” is set to “Low-urgency notifications, do not escalate” as there’s a check-box “Raise urgency of unacknowledged incidents to high” I can tick. Why is this checkbox not available when I select "“Dynamic notifications based on alert severity”? Let me know of an alternative approach. I wanting to avoid having to create 2 services for this.

I’m not sure if anyone encountered similar problem.We just suddenly cannot receive any webhook of pagerduty from Sep26,  the endpoint is definitely reachable and had been working for years.I can see the webhook integration of most services had been disabled,  if I manually enable them , they just got back to be disabled almost immediately.it did happen around my yearly renewal ,so I wonder if it’s something to do with that.

When the internet blinked, teams needed clarity fast.On Oct 20, 2025, a major AWS us-east-1 outage rippled across SaaS, messaging, conferencing, and cloud providers—reminding us that incidents aren’t an if, they’re a when.PagerDuty’s core incident notifications stayed resilient, and our infra + engineering teams took rapid, decisive action to mitigate downstream impact—so responders knew what was wrong and how to act.Resilience isn’t luck. It’s preparation, architecture, and practice. Read how we navigated the outage and what teams can learn: When the Internet Blinked: How PagerDuty Stayed Resilient During the October 20 OutageBy Rukmini Reddy, Sr. VP of Engineering, PagerDuty  

Hi all!I would like to alert on specific incidents containing specific text in the alert, suppressing all other alerts between the hours of 10pm-6am.I have created a service orchestration rule which runs and updates the summary field when the summary field contains the specific text, which I believe then alerts. In that rule is also an else rule to suppress all other alerts. The part I’m having difficulty on is how to enable this rule only during the hours of 10pm-6am. I would appreciate any assistance!

Hi! I was just added to my organization’s PagerDuty rotation, and after setting up the iOS app on my phone and testing out the notifications, I discovered that I cannot adjust the volume of the high-urgency notifications, which are sent as native Critical Alerts. A quick Google for “ios critical alerts volume” shows that controlling the volume of these alerts is not possible as an iPhone user, but it is possible as an app developer; this blog post shows something called “PushOver” allowing users to configure Critical Alert volume on a scale of “loud” to “deafening”. “Deafening” is how I would describe the current volume level of the high-urgency notifications, and this is just not acceptable in my situation: I’m not the only person in my building, and I can hear these notifications outside on the street, two-stories down 😅. I understand their importance, but the whole apartment building doesn’t, and I’m sure to run into problems with the neighbors if I turn these on. Can you pl

Hi everyone,We sincerely apologize for this morning's technical issues that prevented registrants from joining the live webinar with Arize. The full recording is now available.Since you couldn't ask questions live, we've created this thread for Q&A. Our speakers are ready to answer your questions about AI reliability, monitoring, observability, and implementation strategies.How to participate:Watch the recording Post your questions in the comments Get answers directly from our speakersWhether you want to dive deeper into specific topics or discuss how to apply these concepts to your organization, ask away! 

Exciting news for RBA users!PDU has revamped our RBA learning path! 🚀  Whether a user is new to automation or looking to deepen their expertise, this learning path guides users from foundational concepts to advanced operational controls—empowering them to design, deploy, and manage resilient automation at scale.Even more exciting news: We have launched our PagerDuty Runbook Automation Certification!  All users that have access to certifications will see this certification in their PagerDuty University account.  Check out the one-pager about this new certification here, and the study guide for the certification exam here. 

Hello when attempting to run a ansible play via bash script on a remote RHEL 9 node i am getting "ERROR]: Task failed: Finalization of task args for 'ansible.builtin.set_fact' failed: Error while resolving value for 'infoblox_next_ip': The lookup plugin 'nios_next_ip' failed: a bytes-like object is required, not 'str'". This play is using the infoblox plugin to lookup ip addresses, it works great if i run on the remote node local CLI however when triggered from rundeck to the RHEL 9 node i get this error. From my testing it appears to be related to the password and special characters but im not 100% sure. Any ideas on how to troubleshoot?Not working(trigger from rundeck): rundeck -> shell script -> ansible-playbook -> infoblox moduleWorking(local CLI on RHEL Node): ansible-playbook -> infoblox module250 - name: Get next available IP address in given subnet with exclusions251   ansible.builtin.set_fact:252     infoblox_next_ip: >-                          ^ column 23<&

I am new to pagerduty. Trying to set up alerts and escalation policy. nothing seems to work at all. I have set escalation policy repeat alert 9 times if no one acknowledges. and guest what after that change I stop getting any kind of alerts even if I acknowledged it whilst alert is still firing from grafana side.  I doesnt repeat any alert at all for some reason and also creates incidents in a single payload. Why would I want all incidents in one payload. Also do you have feature when alert closes itself once it stops firing from grafana side like it happens in opsgenie. 

Are you passionate about building resilient systems or have a story to tell about managing incidents in creative ways? We want to hear from you! We’re excited to announce the Call for Papers is officially open for PagerDuty on Tour San Francisco 2026. This is your chance to showcase your innovative ideas, share real-world lessons, and connect with a vibrant community of peers and industry experts.Session Guidelines:Session format: Talks (20-30 minutes including Q&A) or Panels (40 minutes moderated discussion) Session topics: Back to Basics, Building resilient systems and teams, Automation and AI in operations, and more - see full list of topics in the submission form Audience: developers/SREs - we recommend providing at least three actionable takeaways fit for a technical audience.Ready to submit your idea? Submit your proposal here by November 14th and help shape the future of incident response, automation, and reliability.We can’t wait to see what you’ll bring to the stage. 

Hey all, I’m utilizing the /incidents API to fetch all incidents for an internal report. From what I can tell the since/until date parameter is filtering based on the created_at date. Does anyone know if there is a way to filter based on the updated_at field? I’d like to incrementally load a warehouse with the incidents from this API, but you can’t really do that if you can only filter by the created_at date.