Recently active topics

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

Within Rundeck, is it possible to restrict the ip source/locations for an api key to be used?  For instance, the “admin” userid’s api key can only be used by scripts/calls from the Rundeck server itself.  Any suggestions on how to restrict the source calling location of specific api keys (as normal regular end-users’ api keys can be from their laptops and such)?

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

After setting rundeck.security.apiCookieAccess.enabled to value of “false”; the “Projects” list pull-down shows an empty list after user’s log into the Rundeck gui.  Granted, the Rundeck home page still shows all the projects.  (Rundeck version 5.20.0)

After upgrading to Rundeck 5.20.0; it looks like the ssj-ssh plugin no longer works with double-quoted commands in the job steps.  For example, the following used to work:<exec>sudo "sh /u01/scripts/sre/myscript.sh ${option.parm1}"</exec> We had to change it to the following in order for it to work:<exec>sudo sh /u01/scripts/sre/myscript.sh ${option.parm1}</exec>With double-quotes, the job returns: [sudo] password for user1:sudo: sh /u01/scripts/sre/myscript.sh userval1: command not found[user1@serverxyz ~]$ echo $?1 Note: This is on Oracle Linux 9 server.

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!

Catching up on the latest month + what's coming next!🌏 June on The Road João Freitas, Chief AI Officer at PagerDuty, welcomes LLMDay guestsSummer is here – and we’re so excited to spend it alongside our community members. This month, PagerDuty team rocked the conference stages across Europe and North America:DeveloperWeek NYC: Mandi Walls moderated a panel “The New Org Chart: Leading Teams in the Age of AI”. Curious how it went? Take a look at the photos! LDX3 London: PagerDuty became a headline partner of LeadDev’s flagship conference. Missed it? See João Freitas’s talk Production AI agents: The gap between promise and reality here. WWCode NYC: Kat Gains delivered a talk Staying in Your Lane: Incident Response for Leaders at Women Who Code Summit in New York City.  SREDay Paris and LLMDay Hamburg: Daniel Afonso talked about the evolution of Incident Response and how leveraging AI Agents can reduce responders’ cognitive load.  LLMDay and SREDay in Lisbon: PagerDuty team hosted both co

So, the clock is officially ticking.With the news that Opsgenie is being sunsetted over the next 9 months, a lot of teams are facing unwelcome architectural crossroads.While a multi-month runway feels long on paper, auditing routing rules, migrating complex on-call rotations, and ensuring zero downtime during a cutover is a major operational lift. As you begin window shopping for what comes next, it helps to look at the two distinct paths forward. Ticketing-First vs. Purpose-BuiltThe Tool Consolidation Path: Moving your alerting into a broader IT service management ticketing or helpdesk platform. While this can look like a low-friction option upfront, it’s vital to look closely at whether a ticketing-centric framework can handle advanced real-time orchestrations—or if it introduces the risk of a secondary migration later as your digital operations scale. The Purpose-Built Path: Transitioning to a dedicated, end-to-end incident lifecycle platform. This approach prioritizes high-fidelity

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 

After upgrading to Rundeck 5.20.0 release; we see the following errors repeatedly in service.log:[2026-06-09T15:59:50,795] ERROR spi.SqlExceptionHelper - Unsupported conversion from DECIMAL to java.sql.Time[2026-06-09T15:59:50,975] WARN  spi.SqlExceptionHelper - SQL Error: 0, SQLState: 22018[2026-06-09T15:59:50,975] WARN  spi.SqlExceptionHelper - SQL Error: 0, SQLState: 22018 This is Rundeck 5.20.0 running on Oracle Linux 9.  The database being used is 8.0.46-commercial and Rundeck is connectiving via mysql-connector-j-9.7.0.jar .  Any suggestions?

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.

This is as simple as it gets, free plan for now, 1 user, I’m always on-call, if I trigger an sms or call test it works as intended to my mobile phone. but I have integration setup with Expel (3rd party SOC), I can see their test alerts arrive in PagerDuty, it shows that it’s assigned to me, status is triggered and I get no calls/text What am I missing? surely it’s something simple I haven’t stumbled on. I have not setup a schedule yet, I figured it isn’t needed if I am on-call 24/7 and that is configured (I just noticed the “complete onboarding” is suggesting that I do that.., but again, the current event is triggered and assigned to me so I don’t think a schedule is needed). Thank you!Martin

Hello,We're using PagerDuty External Status Pages and have noticed that the public status page displays incident history going back several years (currently back to January 2022).Our goal is to show only the most recent 30 days of incident history to customers.I've reviewed the External Status Page settings and documentation but haven't found an option to:Limit visible incident history to the last 30 days Automatically hide incidents older than 30 days Configure a retention period for publicly displayed incidents Delete or archive older incidents from the status pageCould anyone confirm:Is there a supported way to restrict incident history visibility to the last 30 days? Is there an API endpoint or administrative action that can remove older incidents from an External Status Page? Are there any roadmap plans for configurable incident history retention on External Status Pages?Any guidance or best practices would be appreciated.Thank you.

We were recently doing a review of our plugins and noticed that version 2.0.0 is available for the Slack notification plugin. However when checking via “Find Plugins” the community version of Rundeck only shows version 1.2.4. Now from seeing the Rundeck documentation I see the Slack notification plugin is now a Enterprise plugin. So am I right in assuming the Community version will be stuck on 1.2.4?

We're always working to reduce operational friction and context switching for SRE and operations teams. To help protect your focus and speed up your incident response, we are upgrading how PagerDuty interacts with Slack.⏱️ TL;DR: What’s Changing & WhenThe Change: PagerDuty will soon create a dedicated Slack channel for every important incident, eliminating the noise of shared channels. The Timeline: Rollouts will begin on June 8, 2026, and progress in phases throughout the month. You’re in Control: You retain full configuration control. You can easily customize when channels are created – or opt out entirely in your Slack configuration settings.🧠 Why We’re Making This ShiftWe’re making this shift because 7 out of 10 practitioners are still managing multiple incidents inside a single, high-traffic Slack channel – which constantly interrupts their workflow. This is a common and comfortable habit, but stacking incidents this way drastically increases cognitive load and operational fr

Did you miss our latest live stream? No worries! Behind the Scenes: Shift-Based Schedules is now available on-demand.We gathered our mobilization engineering and product teams - Todd Murphy (Principal Product Manager), Kelsey (Sr. Product Designer), Ken (Software Engineer), and MJ (Sr. Engineering Manager), to discuss how PagerDuty is completely reinventing the core scheduling experience.Say goodbye to schedule layers and hello to a scalable, flexible, and modern scheduling experience! WATCH NOW Check out some resources shared during the session: Schedules API​​​​​ Terraform PagerDuty Schedules​​​​ Shift-Based Schedules: Upgrading to the V3 Shift Schedules API​​​​​ Read the deep-dive on the blog ​​ Check out the Knowledge Base​​​​​​ Watch the demo​​​​ Take the Shift-Based Schedules Product Tour​​​​  👉 Register now to the next PagerDuty Live Behind the Scenes: SRE Agent 

Hi all, quick vulnerability question.Our vulnerability software has flagged up Rundeck v5.20 with CVE-2026-22732 because of the component spring-security-web-5.8.15.jar I could not find anything about this CVE in this forum or Rundeck web page.How can we find out if there’s a fix for this coming up soon?Is there a place to report this?Thanks!

We are in Rundeck Version 3.0.24 and internally it is using MySQL 8.0.45. AWS RDS MySQL 8.0 is getting EOS on July 31, 2026. So we are planning for upgrade to MySQL 8.4There is no mention of MySQL 8.4 support in Rundeck offical pagehttps://docs.rundeck.com/docs/administration/configuration/database/mysql.html#configure-mysqlCan you help with the details?