Commons Corner

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?

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)

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

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: 

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 dynamic

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 🏆

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-

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:

Hi,This is a WAR installation on FreeBSD, I added :# Allow donwload of public keysrundeck.gui.keystorage.downloadenabled=truerundeck.feature.publicKeysDownload.enabled=trueto both framework.properties and rundeck-config.properties, which I has to create (it doesn’t exist in FreeBSD) with no success.I also added this to preferences.properties Still doesn’t workRegards,Xavier

Hello,I introduced some times ago a workflow plugin, allowing to create dependency links between jobs that can subsist over the 24h duration of the workflow, which is defined with a daily basis.This can lead, for example, with a job failing for any reason, and the jobs linked to it waiting patiently until the error is fixed, and relaunched. If needed, waiting for the whole night.Since, I’ve worked on tackling the main problem due to linking dozen of jobs together : a visual representation of the jobs and the links between them, through a new UI plugin.Preferably, with an interactive output and able to be updated at will.I’ve reached a satisfactory level with it, where while the desired goal is reached, the UI plugin became more than useful even for people not using the other dependencies modules.To the point it is becoming a companion of the main UI.The

Looking for your next deep dive into the world of DevOps, DevRel, and AI? We’ve got you covered with a two-episode drop! Built for Devs with Tessa Kriesel (Part 2)The conversation continues! In the second half of our sit-down with Tessa Kriesel, Daniel and Mandi dig deeper into the world of DevRel.Tessa unpacks how to build a stronger community around a product and how DevRel bridges the gap between engineering and the user. LISTEN NOW ⬇️ Harnessing AI with Lev AndelmanHow is the "AI Revolution" actually changing the day-to-day for Platform and DevOps engineers? Lev Andelman from Harness joins us to discuss the evolution of Harness Engineering. LISTEN NOW ⬇️

We recently upgraded to Rundeck 5.20 and set “rundeck.feature.nextUiMode.enabled = true”.  While the projects’ job lists load quicker (especially those with numerous cascading folders for job organization), the top of the screen shows duplicate search bars now.

Hello,Some of our users noticed a minor issue with "Job reference" step. There step label value is ignored. When a step label is added to a  "Job reference" step, the job can edition can be normally validated without any message error but the label value just disappears suddenly. It doesn't even appear after saving the stop (before saving the workflow)This happens in both Rundeck Pro/Enterprise and Rundeck Community…Is this a known bug?

Hello,When you add a "Job reference" step to a job, and choose “By name” to manually enter referenced the job’s group/name (rather then using “Choose a job” button and selecting a job interactively), is there supposed to be an autocomplete in jobs names/groups/names ? In both Rundeck Community and Pager Duty

We have enabled the execution history cleanup in Rundeck; however, the executions are not getting deleted as expected.As per the Rundeck documentation, it is mentioned that the cleanup feature needs to be enabled and properly configured. Could you please confirm:Is enabling and configuring the execution cleanup sufficient for automatic deletion? Or do we need to create a separate job to handle execution cleanup?We would like your guidance on the correct approach to ensure execution history is cleaned up as expected.And rundeck version is 3.3.11

For many organizations, the path to "elite client service" is often blocked by fragmented workflows and all-hands-on-deck chaos. At PagerDuty OnTour SF, we’re hosting a fireside chat with Jim Wallace, Operations Admin II at UWM, and Marty Jackson, NA Field CTO at PagerDuty, to discuss how UWM replaced manual intervention with a seamless, automated incident engine.UWM’s journey from a small storefront to an enterprise powerhouse required a radical shift in how they handle observability. Jim will share how they integrated PagerDu

When you are managing thousands of services, "alert fatigue" isn’t just a buzzword—it’s a critical operational risk. At PagerDuty OnTour SF, we are bringing together incident leaders from Twilio and Intuit to discuss how they’ve moved beyond reactive firefighting to build resilient, AI-powered operations.Gandhi Kumar, Principal Incident Commander at Twilio, will share how his team navigates a staggering 60,000+ monthly alerts. By leveraging PagerDuty AIOps, Twilio has successfully cut through the noise, transforming a torrent of data into targeted, actionable signals. Gandhi will also provide a "view from the commander's seat," offering har

Hello,Is there a way to reference a job from another WITHOUT the referenced job’s project name ?Some of our users use the SCM plugin to push job definition to a GitLab instance and share the referenced same jobs between two Rundeck instances used for two different purposes. Lets call them Instance A and Instance B.Instance A has project_X containing a referenced job_1, from job_2. Both jobs definitions are pushed to GitLab instance and cloned to project_Y on Instance BThe problem is, while the UUID and jobs name are the same on both Instance A and Instance B because both jobs do the same EXACT thing as you would except (no modification on actual jobs, they different only in terms of which nodes they’re scheduled/executed on), projects names on tho other hand reflect the purpose/environment (testing, production, level-

As the role of the engineer evolves, we are moving beyond siloed AI tools toward a future of true agent-human partnerships. To explore this shift, we are excited to feature a session at PagerDuty OnTour SF with Jonas Nelle, Head of Engineering for Agents at Cursor, and Rukmini Reddy, SVP of Engineering at PagerDuty.This discussion will dive into how organizations can move from reactive recovery to predictive resilience. By utilizing protocols like the Model Context Protocol (MCP), teams can provide agents with a unified view of their codebase and PagerDuty incident history. This integration allows agents to bridge the gap between cod