Solved

Hi,We just upgraded to PagerDuty 5.20. Since then, apparently, our IDS consider the new GenAI plugin as "malicious" and blocks its download.https://rundeckpro.tld/assets/pro/ui-components/GenAi.umd.min-85142c85b32d5e5ead5945256e58c753.js fails at 2.7MB (connection reset)Is there a way in the configuration files to completely disable this plugin, which we do not use ? It does not appear in the system (gear) menu as indicated in the docThis plugin does not neither appear in the plugin managerWith this problem, the UI takes dozens of minutes to loadRegards,Xavier

Hello.I noticed there is a weird difference between the two timestamps shown in Rundeck 5.19 web interface.I’m referring tot he HH.mm:ss timestamp shown in the left sidebar, which I assume to be the server’s timestamp in local timezone and the ISO8601 timestamp shown in tooltip/.rdlog file. The problem is they look inconsistent so I was wondering how each of these timestamps is determined The timestamp form tooltip/.rdlog file has a Zulu suffix which suggest UTC but there is a huge inconsistencyThe server is located in France (UTC + 2), locale timezone is set correctly in the OS, so is the UTC clock. NTP synchronization is active. Therefore on Rundeck server, both local timezone and UTC are set correctly.Rundeck JVM is executed with the correct timezone parameter “-Duser.timezone=Europe/Paris”. But the problem is there is much more than 2 hours differences between the left sidebar timestamp and the ISO8601 tooltip timestamps.I noticed the issue issue in job during it’s execution on the

At our organization we generate PagerDuty incidents by using email alerts.The emails are sent to service integrations. Each service has an individual email. So even without Global Orchestration, we can process the emails into useful incidents using the Service Orchestrations. We aren’t licensed for AIOPs, so we can’t currently use Global Orchestrations.A typical email might from our SCOM monitoring and have a subject line something like  “ SCOM: Health Service Heartbeat Failure Resolution State: New” or from one of our storage systems like “Storage D1A: Warning filesystem <filesystem> at 80%”.This email is sent to our PagerDuty integration email and processed using the Service Orchestration rules. For repeated alerts, we can set a custom dedup_key such as the server name or filesystem name. If the dedup_key matches on subsequent alerts, then PagerDuty appends the new alert to the old ticket.In addition, the dedup_key allows us to close incidents indirectly by using an event rule:

Hi, first time poster. We really love our PagerDuty slack integration, and it’s been providing us excellent response times and clarity for our on-call rotation.We emphasize clarity of alert names, priority levels, affected services, and incident urgency in all of our alerts. We were surprised yesterday when all of a sudden, all of our alerts had emojis attached to them. This has made our experience very confusing and cluttered, and we’d like the ability to turn this off. Is this possible, and if not, is it possible to remove these entirely?

We get a published rotation of people covering the next 30 days from an outside vendor so the schedule changes every month. I don’t see an end date for a layer. - like starts Monday 3/16 and ends Friday 3/20. Right now the schedule just repeats ad nauseam even though we don’t have the schedule for April yet. Our old paging system allowed Start On and End On dates. Does PagerDuty have that mechanism?

Created our first Custom Field on a Service, a single select list to identify the Engineering Team responsible for that Service. I was hoping that we could set it up in a way so that when a responder receives an alert for a new Incident, since each Incident is paired with the appropriate Service, we could also display that Engineering Team custom field on the Service, at the Incident level. However, in reality it appears that the Custom Field on the Incident is not related in any way to Custom Fields on the Service.  Is it possible for me to display custom fields asociate with a Service, on incidents related to that service, so that on-call responders can see that info and I don’t have to manager an entirely separate custom field at the Incident level? Thanks! 

The new Slack integration update now @mentions the assigned user directly in the incident message posted to Slack channels. While this is great for high urgency incidents where immediate attention is needed, it's disruptive for low urgency incidents.Our team uses separate Slack channels and PagerDuty services for high vs low urgency alerts. Low urgency alerts have long SLAs and are triaged on a best-effort basis during business hours. Getting repeatedly @mentioned in Slack for these creates unnecessary noise and distractions throughout the day.Is there a way to control this behavior that I'm missing? Ideally something like:A per-service setting to enable/disable user tagging in Slack messages A per-urgency setting (e.g. only tag for high urgency)If not, would love to see this added as a configuration option. Currently there's no way to suppress the @mention without either muting the channel entirely or removing the native Slack integration, both of which lose visibility into the alerts

Hi folks, if a Responder who was previously deemed not needed for an Active Incident is now needed to be re-engaged, how do you accomplish this?

PagerDuty has an option to “Send a Webhook POST” in an incident workflow. I’m trying to set an automation incident workflow based on a specific custom incident type. My final step is to include the resolution note, but I’m not seeing a way to do this. It sounds like something any average user/customer would want to hear about (e.g. I want to know what the resolution was to the incident), but why is it not available as a field? Or does anyone have a workaround on how to capture it?In the body of this text field, it shows a bunch of incident-related options, including “resolveReason” which to a regular human seems like it would be the same thing as “resolutionNote” but it’s not. It seems to only be used to determine whether it was a merged incident or not. Is anyone in the same situation? I can’t be the only one who wants to query the resolution of an incident so we can send communications around it. This seems like a severe product gap that I’m surprised hasn’t been addressed. I know Pa

HiI tried to use the PD MCP in VSCODE for auto create Schedule Overides but I’m always getting the error: “Sorry, no response was returned.” My MCP config is below:"io.github.PagerDuty/pagerduty-mcp": {"type": "stdio","command": "uvx","args": ["pagerduty-mcp==0.2.1","--enable-write-tools"], “Get” operations are working fine. My request is: schedule_id: "P76S19G"override_request: {  "start": "2026-02-08T18:00:00+02:00",  "end": "2026-02-09T08:00:00+02:00",  "user": {    "id": "PNBBMSL",    "type": "user_reference"  },  "time_zone": "Asia/Jerusalem"} will appreciate any help here

Issue Summary:We're experiencing a problem where ServiceNow incidents triggered by Solarwinds alerts are not creating corresponding incidents in PagerDuty, even though they meet the priority criteria (P1–P3).Context: Solarwinds is our alerting tool, integrated with ServiceNow (Yokohama, PD Spoke 1.4.0, PD 8.2.0). ServiceNow is configured to forward P1–P3 incidents to PagerDuty. We're using assignment group services only in PagerDuty (no business/technical services). This issue began after integrating Solarwinds through ServiceNow Event Management. What we've observed: Some PagerDuty webhooks become disabled intermittently, though health checks often return normal. The issue is inconsistent—not all Solarwinds-triggered SNOW incidents fail to generate PD incidents. We suspect a possible problem with the PD Spoke workflow or webhook handling, but haven't confirmed. If anyone has run into a similar issue or has suggestions on what to check next, I’d greatly appreciate your insigh

I have a Pager duty system in which i can add up to 3 phone numbers to get notify about an alert.Now my question, is there any possibility to add n number of phone numbers..?

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.

Apart from alerts, all notifications I received from Pageduty is showing redirect urls as it is not like embedded in the anchor word. Simple words it is not HTML card, just plain text.Does anyone faced this?

I have set up my phone and sms, verified them, and sent myself test messages. However, the Onboarding banner still wants me to do this. I have set it up, verified, sent tests, sent tests, and sent tests. But, it doesn’t help.Then, I deleted them, re-added them (phone and sms), verified them, tested them. The tests come through, but the onboarding wizard still says I need to “receive a test notification”. It is the only item left in the onboarding list. Help! How do I get the onboarding wizard to go away?

Hello, is there a way to "Kill tracked processes after execution" the PID child when i kill a job that running for a specific command(Not a job)? 

Hi,Where I live, we use 24 hour clock, we start the week on Monday, and date format is dd.mm.yy. How do I select this in the web interface?I’m running on a EU instance, why is 12 hour format default?

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.

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?

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!

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<&