Recently active topics

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.

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

Ever wanted to manage your system incident triage entirely from a chat interface without constantly jumping between windows?In our latest MCP Community session, Engineering Manager José Reyes and Forward Deploy Engineer Ignacio Garces team up to show you exactly how to unleash the power of the Model Context Protocol (MCP) server alongside the ServiceNow plugin.💡 What you’ll see in this episode: The New Releases: A quick overview of brand-new updates, including OAuth token support via environment variables, agent-driven orchestration rules, and integration with the V3 Schedules API. Bi-directional Magic: Watch how a single prompt inside Visual Studio Code automatically provisions a high-urgency incident across both PagerDuty and ServiceNow simultaneously. Seamless Triage & Sync: See real-time chat commands dynamically update assignment groups, change ticket statuses from New to In Progress, and push live investigator notes across both platforms instantly. Quick Navigation: A

Hello Everyone,I’m a Devops Engineer , who worked with rundeck for few years, both for personal and profesional projects.I’m trying to use Rundeck “remoteURL” feature to list as values some informations regarding container stacks on dockhand platform.Everything is collected and working perfectly when dockhand authentication is disabled, but when authentication is enabled, i’m unable to make it work. Dockhand can only authenticate on API with a bearer token that it generated like in this call :curl -X GET -H "Authorization: Bearer dh_mytokengeneratedbydockhand" https://dockhand-platform.test/api/stacks?env=1 -s | jq .[].name"dockhand""gitlab-ce""technitium"But i’m unable to reproduce this behavior with remoteURL configuration. I did try to add my token in rundeck key storage, in “password” type , then select Bearer in authentication type and filling the rundeck key. The result seems to always be a 401 unauthorized error, and it seems that if I edit my job again, the authentication field

Catching up on the latest month + what's coming next! Highlights 🏆 Introducing: PagerDuty ChampionsWe’re excited to announce PagerDuty Champions, a new contributor recognition program designed to amplify the most engaged practitioners, customers and partners. Get the tools and connections you need to make a real difference while growing your own career! Learn more and apply today 👈 Applications are open: It’s time to get recognized 🏆 ✨ New forums: Rundeck & MCP PD Commons has two brand-new forums. Jump in to share new plugins and best practices, ask questions, read the documentation and be part of the open-source communities.Rundeck Community: your go-to hub for all things runbook automation. MCP Community: A dedicated space for everything related to the PagerDuty MCP Server.🎤 On the RoadWe kicked off the month with the Agents Day Hackathon, in Lisbon. Daniel kept it going in Germany at the Berlin AI Meetup, exploring how AI agents are fundamentally reshaping incident response.

This is your go-to space for everything related to the PagerDuty MCP Server. Below are the key resources to get you up and running:📚 DocumentationSupport Docs — Setup guides, configuration, and troubleshooting https://support.pagerduty.com/main/docs/pagerduty-mcp-server Developer Docs — MCP tooling & remote server reference https://developer.pagerduty.com/docs/mcp-tooling-remote-server🛠️ Technical ReferenceAPI & Tool Reference — Full interactive documentation https://pagerduty.github.io/pagerduty-mcp-server/ GitHub Repository — Source code, issues, and contributions https://github.com/PagerDuty/pagerduty-mcp-server📢 What's New?Want to stay up to date with the latest features, security updates, and bug fixes? Watch our recent MCP Community Live recording!Have a question? Drop it in the forum.

Hello and welcome! Whether you are a long-time Rundeck user, a brand-new contributor, or just exploring what’s possible with runbook automation, we are thrilled to have you here.This dedicated section of the PagerDuty forum is a space for all things Rundeck. To keep this community helpful, healthy, and high-powered, we have a few simple guidelines:🤝 Code of Conduct (The Quick Version) Ask & Learn: No question is too basic. Ask about configurations, jobs, or specific use cases. Share the Knowledge: Discovered a cool workaround? Built a great workflow? Share your tips and tricks with the class! Be Helpful & Respectful: We are all here to learn from one another. Lift each other up and keep discussions constructive. 📚 Essential Rundeck ResourcesGot questions or want to dive into the code? Bookmark these essential links: Official Documentation: The ultimate guide for setup, configuration, and feature guides. Check out the Rundeck Docs. Found a Bug?: Help us make Rundeck bett