Ask a product question

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 

Hello, is there a way to filter like on the website to show only the last 30/90 days instead of all?ThanksJoe

We currently use an on-call schedule to monitor factory equipment overnight.e.g. Monday-Friday from 6pm to 6am.We would like to receive the alerts into PagerDuty during the 6pm-6am time frame, but only notify the on-call technician from 4am to 6am for any alerts received.This gives them time to respond before day shift starts.Is it possible to configure PagerDuty to queue alerts in this manner? 

Recently a service that uses the email integration to create incidents has started creating duplicate incidents even though only one email was sent. The service was setup ~ 2 years ago and this started in the last several weeks. Duplicate incidents happen every couple minutes. Is anyone else running into the same problem?

I used an event rule (under the Service Orchestration) a couple years ago to suppress a particular alert for a small window which worked.Working rule: (now in Mon,Tue,Wed,Thu,Fri,Sat,Sun 16:11:00 to 16:26:00 America/Los_Angeles) and (event.summary matches part exactly '**ST(MGAS) Grid Application status: CloudSuite ** Base-******-EventHub')Recently I’ve added a similar rule but for a particular day and time but the alert triggered any way.Failed rule: (now > 2026-10-09 21:00:00 Asia/Singapore and now < 2026-10-10 01:00:00 Asia/Singapore) and (event.summary matches part 'Deployment Replicas Unavailable')Has something changed that doesn’t allow this type of rule or am I doing something wrong?Thank you.

We are looking for guidance on PagerDuty call-event visibility and escalation behavior.We have already made several follow-ups with PagerDuty Support on this issue, but have not yet received a substantive response. As this is affecting operational monitoring and audit requirements, we would appreciate your help in treating it as a top priority.In our environment, calls can be received by the on-call responder but may not be acknowledged through the IVR prompt. In these cases, we need to understand:• Why the call attempt is not visible in the incident timeline or other reporting views.• Whether there is a supported configuration, log, or reporting option to retain a record of all call attempts, including unanswered or unacknowledged calls.• Whether an unanswered or dropped call can be routed to the next level of the escalation policy.• Whether there is a recommended workaround or roadmap item for complete audit visibility of call attempts.We would appreciate guidance on a supported solu

We are trying to integrate with HALO. Our initial integration had some odd and concerning behavior, however.The webhook configuration on the PagerDuty side is limited by scope to a specific service. However, when we enabled the integration on the HALO side it automatically upgraded priority to incidents assigned to OTHER services outside the scope of the webhook. We are trying to track down the issue, but I’m curious if others have experienced an issue like this.

Hi I a the maintainer for Rundeck on FreeDSD.I’m in the process to upgrade from 5.20.1 to 6.0.1 When I start Rundeck I got this stacktrace : PreBootstrap process rundeckapp.init.prebootstrap.InitializeRundeckPreboostrap failedorg.apache.logging.log4j.core.config.ConfigurationException: No type attribute provided for component log4j at org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.createComponent(PropertiesConfigurationBuilder.java:362) at org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.processRemainingProperties(PropertiesConfigurationBuilder.java:206) at org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.build(PropertiesConfigurationBuilder.java:190) at org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:56) at org.apache.logging.log4j.core.config.properties.PropertiesConfiguration

Hihttps://diva-e.pagerduty.com/my-on-call/monthis there a way to have the week starting with monday? not only because our shifts rotate at monday but because or work week always starts at monday (in Europe).ISO-8601https://www.epochconverter.com/weeks/2025it’s exremly confusing to have my-on-call shift calender starting at sunday! IMHO everybody uses the word <weekend> in reference to saturday and sunday?! it’s named weekEND, therefore the week always starts at monday, not at sunday.greetings from Germany (U.S.E. ;)Stefan K.

Based on the Pagerduty documentation, it seems like “description” field is no longer supported and only the “title” can be retrieved via webhook. These two fields are very different, as one is a quick summary and the other provides scope and context necessary to understand an incident. Is there a workaround to retrieve the description field via webhook? This is normally where we would put a paragraph of additional critical context as such as the Slack thread of a user-reported issue, details about the scope of the issue, etc. Does anyone have any advice on what to do?

If I want to replace a colleague who is on a 1000-1800 cover each day for a week. Another user covers out-of-hours. I click on the rota’d day and it comes up with my username, the date and the time slot. I expect that if I extend the dates to cover the week and leave the timeslot as is, that it will exactly replace the slots the original user was covering. Instead it puts them on 24 hour cover for the week. Instead I have to replace every day, one at a time (boring)This feels like a bug to me. If the time slot is there and you can select multiple days then it should apply to each day. If it is not to work like that, there should be a start and end time for the whole period.Is this something that is likely to be fixed or is there a workaround that doesn’t involve clicking on multiple days and doing the same thing on each.  

Hi team,I have previously read through some older posts about implementing SSO for Rundeck Community version and it seems this is only available for Commercial/Enterprise versions.However, I’d like to know if we have alternatives to do that on Community. I saw some posts suggesting pre-auth mode, how could we implement it or even implement other solutions to have SSO on our environment?

The PagerDuty Mobile App documentation for iOS (https://support.pagerduty.com/main/docs/mobile-app-settings#configure-ios-devices) states:"When you are added as a Responder to an incident, the iOS mobile app will always use the PagerDuty Alert ringtone for push notifications."Could you explain why this behavior is implemented? Why can't responder notifications use the same custom notification sounds as other push notifications?Are there any plans to make this configurable in future releases?

We have multiple services connected to the same Slack Notification Channel.Historically, when an incident was reassigned between those services, the existing Slack incident card was updated, including the Service field. Recently, without any configuration changes on our side, PagerDuty began posting a second incident card for the same incident when the service changes.Interestingly, subsequent incident updates (we use the Thread incident updates option) are still applied to the original Slack post rather than the newly created one. This suggests that PagerDuty is still able to correlate the Slack message with the incident, making the additional post redundant.Expected behaviorReassigning an incident between services that are connected to the same Slack Notification Channel should update the existing Slack incident card, including the Service field.Actual behaviorA second Slack incident card is posted when the service is reassigned. Subsequent incident updates, such as status changes, c

I’m trying to set up a filter to show incidents trigger outside of core business hours. But the business hours interruptions filter variable doesn’t show it’s accepted values/how to use it. It explains here what business hours mean but not what the value should be below: 

Hi allLooking for help pinning down where Scribe's transcript routing is decided.Setup:- Production incident is declared in PagerDuty, which kicks off an Incident Workflow.- The workflow creates a Zoom meeting, then creates a dedicated Slack channel for the incident, then adds the PagerDuty Advance Scribe Agent. Scribe joins the Zoom call and posts the live transcript to Slack.Problem:- The Scribe transcript is being posted to our `#alerts` channel (where all our alerts land), instead of the dedicated incident channel created by the workflow.What I've already checked:- Workflow action ordering is correct "Create a Slack Channel for an Incident" runs before "Add PagerDuty Advance Scribe Agent."- Scribe Agent settings have no option to select a target Slack channel.- The "Add PagerDuty Advance Scribe Agent" workflow action also has no channel/surface input.Questions:1. What determines which Slack channel/surface Scribe posts the transcript to? 2. If we have `#alerts` mapped to the servic

See title

We are setting up a PagerDuty status page, and we have created a lot of services specifically for the status page. From this topic we know that if nobody is on-call for the escalation policy of the service, incidents will not be created.However, since the services are used just for the status page, there should be nobody on-call because the alerts are responded to elsewhere (or handled automatically). What is the recommended way to create incidents to update the status page, without spamming someone with useless alerts?

We upgraded our non-prod instances to Rundeck 6 this morning and immediately lost our admin access. Admin access is granted to specific Active Directory groups in an admin.aclpolicy file. I’ve noted that in the service.log when I log in, it DOES list all the user’s groups on login, however when checking the user profile after logging into rundeck, no groups are listed. It’s as though it’s pulling the Active Directory group memberships, but not applying them correctly to the rundeck user object.Please advise if you need to see any of the specific config files (jaas-activedirectory, admin.aclpolicy, etc) to help with this.I did go through the activedirectory conf file and confirmed that all the properties there still matched the documentation on the Authentication page. Not sure where the breakdown is or if anyone else has seen something similar. I saw no notice of deprecation affecting jass or active directory in the release notes...

Hi Team,I’m configuring Azure SSO (OAuth2) for Rundeck using the official documentation:https://docs.rundeck.com/docs/administration/security/sso/azure-sso.html I have successfully created an Application Registration in Azure AD and configured the required values in my rundeck-config.properties file.However, after restarting the Rundeck server, the changes are not taking effect.When I access: https://rundeck.company.com/it redirects to: https://rundeck.company.com/user/logininstead of initiating the Azure SSO flow. Current rundeck-config.properties file Configuration: # rundeck-config.properties: Azure SSOrundeck.sso.loginButton.enabled=truerundeck.sso.loginButton.title=Login with Azurerundeck.sso.loginButton.url=oauth/azure rundeck.security.oauth.azure.autoConfigUrl=https://login.microsoftonline.com/<DIRECTORY_TENANT_ID>/v2.0rundeck.security.oauth.azure.clientId=<CLIENT_ID>rundeck.security.oauth.azure.clientSecret=<SECRET_VALUE>rundeck.security.syncOauthUser=true# Az

Hi team,Is there a possibility or setting we need to be aware of where users will be able to log in via SSO even though they are not assigned to the SSO AD?Thank you!

Hi,We have a schedule that runs every day from 9am to 5pm.Now, we would like to adjust the end time for a specific date, e.g. this Friday but not every Friday!Is there a way to achieve this?Cheers

How do i get mutile team members in a schedule at a given time. Ex: Monday - Friday 8:30AM - 5:30PM I need Bob, Sarah, Jim, Bayley Tuesday - Friday 8:30AM - 5:30PM I need Bob, Sarah, Jim, Bayley, Fred ( Fred comes in on Tuesday ) Saturday - Sunday Fred

I would like to create a rotation schedule that is only active on alternate weeks.Week 1 : Person 1Week 2 : InactiveWeek 3 : Person 2Week 4 : InactiveI can easily create gaps inside of a week using restrictions, so this would be easy to do:1st Half of Week 1 : Person 12nd Half of Week 1: Inactive1st Half of Week 2: Person 22nd Half of Week 2: InactiveBut I cant figure out Week On, Week Off. Is there a way other than restrictions I’m missing?(I realize I could add a dummy account to fill in for the inactive weeks, I would prefer not to do that)

Hi, I want my team to be on call 3 days at a time, with no weekends. This doesn’t seem to be possible, when I add the restriction of Monday to Friday, the scheduling of the 3 days for each person still runs into the weekend.I even tried to add another layer with just one person on it at weekends to try and block these days out, but it still doesn’t work.You can see in the image for example 6th December, Jake comes on the rota for only half a day, because the schedule is still running him through the weekend, even though weekends are excluded.It should be (from the start)David - Monday Tuesday WednesdayJake - Thursday Friday MondayMark - Tuesday Wednesday ThursdayGerald - Friday Monday Tuesdayetc. Surely this is a relatively common requirement - there must be a way I can do it? What restrictions do I need to set? Any help would be appreciated!Thanks,Davidcurrent restriction config