Ask a product question

Hello I was wondering what is the data retention policy for the alert as how long alerts/incidents data is kept in the pagerduty. I couldnt find any settings/config for that or any documentation.  Mehran 

I’m noticing a recent change in the mobile app where resolving an incident via swipe now requires an extra confirmation tap. Previously, a single swipe action would immediately resolve the incident with no additional interaction.This new flow adds extra time, especially when handling multiple low-severity or routine incidents. What used to be a quick one-gesture action is now a two-step process, effectively doubling the time required to resolve each incident.Is there a setting, or a way to revert to the previous workflow? I’ve disabled any requirement for resolution notes in the confirmation screen but it still requires that secondary workflow.

We use the ServiceNow V7 integration in production. It works fine, but we want to move to the generic V3 webhook. We have a lot of services on V7, so the plan was to switch just a few to V3 first and handle the rest later.In our test environment, when we moved one service to the V3 webhook, the other services using V7 stopped working. So we’re trying to confirm what will happen in production. If we switch a single service from V7 to the V3 webhook, will the remaining V7 integrations break? Or can V7 and V3 run side by side? We want to know if this is an all-or-nothing change.

My requirement is to repetitive alerts until issue is resolved, for an exmaple, someone in ,y team resolve the issue by mistake  but actual  issue is not resolved in this casr alert should be triggered in every 5 minutes bcz cloudwatch send only an alarm to pagerduty

I'm struggling with a job in Rundeck that includes an Ansible script, and I'm a bit confused about the node selection behavior.Is it possible to prevent a job from running on all nodes when “Change the Target Nodes” is unchecked? It feels contradictory that:the UI offers “Select All” and “Select None”,the job fails if no nodes are selected,but if you uncheck “Change the Target Nodes” entirely, it just runs on every node anyway.I assumed there must be a way to force explicit node selection before running the job, but I haven’t found anything in the documentation.This is the screen I'm referring to: 

So all of our services have multiple environments like Prod, NonProd, Dev.  Should these be created as different technical services under the same business service, or different business service?  Is there a native concept of environments that I am missing? 

We’ve recently switched our incident response process to using responders when needing to pull in additional resources.  In this case we are using an escalation policy with multiple users on step 1, but only one of the users is getting notifications in this case.It is still adding everyone as a responder, just seems to be randomly choosing one of them to notify.  I’ve verified the following:There are multiple people in the first step of the escalation policy The escalation policy does not have the “round robin” enabled each person in the escalation policy has valid high urgency settings and no pending validation steps in contact info each person is showing up as a responder in the incident when using the escalation policyIs this intended behavior? 

I’ve been trying to request a developer account via https://developer.pagerduty.com/sign-up/ as I’m building an integration but repeatedly get this error An error occurred while attempting to sign up. Please try again later.

Use the Shift Agent to Save Minutes on Overrides in SlackThe Shift Agent can automatically detect on-call conflicts, find coverage with agentic teammate recommendations, and complete overrides all with two clicks in chat. PagerDuty’s Shift Agent in Slack and Google Calendar Integration are generally available.  

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

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

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.

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

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. 

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.  

Hi, in the get incidents api the list of acknowledgements gets cleared after it has been resolved/triggered, why is that? Can we please preserve the list of acknowledgements, we need this data for our reporting

Hello,Am trying to setup rundeck :4.11(with customized docker image) with MySQL azure:8.0.42 as database.Am struck with the liquibase below error:Issue:“Caused by: liquibase.exception.MigrationFailedException: Migration failed for change set core/WorkflowWorkflowStepPrimaryKey.groovy::1653585641550-1::rundeckuser (generated):     Reason: liquibase.exception.DatabaseException: Incorrect table definition; there can be only one auto column and it must be defined as a key [Failed SQL: (1075) ALTER TABLE poc_rundeck.workflow_workflow_step ADD id BIGINT AUTO_INCREMENT NOT NULL PRIMARY KEY]        at liquibase.changelog.ChangeSet.execute(ChangeSet.java:696)”.  When I tried the same instance on flexible server database with MySQL:8.0.25, it is running without any error.I have done all the prerequisites mentioned in the official documentation regarding “sql_generate_invisible_primary_key > Change its value to OFF”, sql mode also off. But still getting the same error. (Using MySQL as a databa

For the past few weeks when I try to “acknowledge” an incident, it ends up snoozing it by default. I then get woken up 10 minutes later despite the acknowledgement. Very, very annoying. 

Hi PagerDuty team! 👋I'm trying to get custom details from Grafana alerts to display in our Slack notifications, but only seeing basic information.Current Setup:✅ Grafana → PagerDuty integration working (using Events API V2) ✅ PagerDuty → Slack integration connected (service: my-service-prod → channel: #team-alerts) ✅ Alerts are flowing through successfullyThe Issue: Our Grafana alerts send rich custom details to PagerDuty (verified in PagerDuty incident view):severity: "critical" namespace: "production" pod: "api-service-7d9c5-xyz" cluster: "us-west-2-prod" component: "api-service" description: "Pod is in CrashLoopBackOff state..." runbook_url: "https://wiki.internal/runbooks/..."However, in Slack we only see:🔴 Pod CrashLoopBackOff AlertService: my-service-prodUrgency: Low[Acknowledge] [Resolve]What We Need: Display the custom_details fields in Slack notifications so our on-call engineers can see critical context without clicking through to PagerDuty.What I've Tried:Configured PagerD

I am needing to create a DuPont schedule in PagerDuty and having a hard time.  Has anyone ever created a true DuPont schedule that can help?

Hi allPagerduty has been working fine for me for years, but today as I’m about to go on call, its started doing this, and then just quits.I tried reinstalling the app but it just quits with the same message even before I can loginI’ve got a stock Google Pixel 7a running Android 16Anyone know whats going on?CheersL 

I am trying to understand the best way to set this up.  I need all incoming alerts to be high priority I want any alert that comes in between 9-6 to not route to the on call tech.  anything outside of those hours will get routed with high priority so the onca tech is alerted and called.