Recently active topics

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

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 Team,I am setting up rundeck with Hashi Corp Vault, as part of setup process and testing found below issues, If anyone overcame these, please let me know the workaround steps.Rundeck version installed: 5.10.0Issues: I tired installing vault plugin, but rundeck did not recognize this plugin, so i ended up installing from Rundeck UI. Vault Storage Plugin version installed: 1.2As per rundeck documentation, this supports KV Engine V2, if we add parameter “rundeck.storage.provider.1.config.engineVersion=2” but this plugin is still using only KV engine V1. Once all the configuration is completed, restarted rundeck service, and was able to make successful connection to vault and able to see the keys, but as per our environment, we kept the vault token expire for 5 mins, once this expired rundeck is not auto using the new vault automatically. When rundeck lost connection to the vault due to token expiry, all jobs are failing irrespective if the jobs are using the keys from vault in the jobs

If your team uses Slack and PagerDuty, you might be interested in [pd-oncall-chat-topic](https://github.com/PagerDuty/pd-oncall-chat-topic). It's an open source AWS Lambda bot that automatically updates your Slack channel topics with who is currently on-call. We've recently added support for shift-based schedules (PagerDuty's new schedule type). Previously the bot only worked with the older style schedules and shift-based schedules would cause it to display spooky data. Setup instructions are in the repo!

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?

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

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

Come hang out for some examples of Custom Shifts, a feature of our new Shift-Based Schedules. Live on Twitch, LinkedIn, and YouTube! July 9! 

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

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