Platform Release Notes

Scribe Agent’s automated incident meeting transcripts are now enhanced in quality and readability. Filler words, redundant statements and profanity are removed to get cleaner summaries of what was discussed — enabling sharper AI-drafted status updates and post-incident reviews. Learn more.

Scope PagerDuty Advance access to specific teams via the AI settings console (requires Account Admin role). This empowers organizations to enforce compliance boundaries and roll out AI adoption with confidence. Learn more.

Event Enrichment automatically pulls context from across your systems (i.e. CMDB, developer tools, and CSV files) directly into your events, with flexible controls for account-level defaults, service-specific overrides, and team-based access, giving tools like the SRE Agent a 360-degree view of your environment so responders spend less time hunting for context and more time resolving incidents. Sign up for Early Access today.

Elevate the quality and readability of Scribe Agent’s automated transcripts from incident-related conference bridges. Remove filler words, redundant statements and profanity to get cleaner summaries of what was discussed — so you can generate even sharper status update drafts and post-incident reviews with PagerDuty Advance. Sign up for Early Access.

Accelerate triage and diagnosis by connecting your stack to the PagerDuty Advance SRE Agent. Use the new SRE Agent connectors and tools configuration experience to easily add integrations for the SRE Agent via MCP or API. Get access to over 20 connectors, including Splunk, Datadog, Observe, Dynatrace, and more. Generally Available to PagerDuty Advance customers. For a full list of available connectors and tools, click here.

PagerDuty’s new homepage is a command center for customers on Operations Cloud Essential/Plus/Ultimate plans. The new homepage surfaces the most critical information, like active incidents, on-call schedules, and quick actions. Eliminate context-switching and access everything you need from a single view, reducing MTTR and allowing your team to focus on high-value work. Learn more about PagerDuty Operations Cloud plans here.

Scope PagerDuty Advance access to specific teams via the AI settings console (requires Account Admin role). This empowers organizations to roll out AI adoption with confidence, as teams can stage controlled AI rollouts, pilots while enforcing compliance with organizational boundaries. Learn more and sign up for Early Access.

Jeli will reach End of Life on December 22, 2026. We’re enhancing incident analysis with Post-Incident Reviews in the PagerDuty web UI (in EA) and recommend that customers transition from Jeli to this new, upgraded capability. More details about how customers can migrate existing Jeli post-incident review data will be sent before the EOL date.

As part of our ongoing Slack updates, the "Stakeholder Notification Channel" is now the “Announcement Channel.” This is a name update only and does not affect your Slack configuration or workflows. Learn more.

Using the PagerDuty Claude plugin or the SRE Agent configuration page, users can configure Skills to arm the SRE Agent with instructions, scripts, and resources that give it specialized capabilities and domain expertise. This allows the agent to intelligently deduce the next steps for troubleshooting issues, even before a human looks at the incident. Available for early access for PagerDuty Advance customers. Learn more and sign up.

The new Events tab in your Analytics console is more comprehensive than ever — and available to all users. Break down event volume by outcome (Triggered, Suppressed, Dropped, and Resolved) and sub-outcome, to see exactly where your events are going and why. In the Events Breakdown table, slice data by routing key, service, integration, and team to identify top noise drivers without manual toil and additional support. Learn more.

Starting June 8, PagerDuty's Slack integration will start rolling out the automatic creation of a dedicated channel for every new incident matching your organization's top two priority types (e.g., P1/P2, Sev-1/Sev-2, or custom names), consolidating all incident communication, actions, and audit trails in one place to reduce noise in shared channels and accelerate your response. Teams can opt out or customize auto-creation rules (by priority, service, and more) via Slack configuration settings. Rolling out in phases to all PagerDuty customers with Slack integration. Learn more or watch this short video.

The SRE Agent helps streamline incident response by analyzing configured Incident Workflows and evaluating them against the real-time context of each incident. The SRE Agent then intelligently recommends the most relevant workflow to run, ensuring faster, more precise, and context-aware incident response. Recommendations include an explanation of the reasoning and a potential ranked list of workflows. Generally available for PagerDuty Advance and AIOps customers. Learn more.

Shift from reactive to proactive operations by leveraging AI Orchestrations to identify actions to automate based on past responder behavior. Using machine learning that has been fed historical event and incident data, AI Orchestrations will suggest actionable Event Orchestration rules to create event-driven automations. Generally Available for AIOps customers. Learn more.

Post-Incident Reviews now use native AI to automatically generate comprehensive review drafts, including summaries, key timeline moments, root causes, and suggested follow-ups. The AI is powered by automatically-ingested data from Slack, Scribe Agent, and Incident Log Entry (ILE) events, turning hours of manual work into minutes of refinement. Teams can comment and collaborate live with @mentions to expedite the review process. Early Access for IM and CSOps customers on Professional plans or higher. Sign up for Early Access.

The June MCP release brings new tools for authentication, scheduling, orchestration, and automation. Engineers can now:

• Connect using OAuth tokens with flexible auth configuration via environment variable
• Manage Event Orchestration rules through AI agents
• View live service status directly from get_service and list_services
• Access accurate on-call data with v3 Schedules API support
• Build AI Orchestrations for Terraform-managed environments
• Extend agent workflows with Webhooks and Extensions support

Learn more about PagerDuty MCP [here](https://pagerduty.github.io/pagerduty-mcp-server/).

Microsoft Teams users can now access Insights Agent directly in chat. Ask plain-language questions to get on demand answers on incident volume, team performance, service health, and more—no manual toil, no analytics expertise required. Proactive operational recommendations, and the ability to act on optimization opportunities with just a few clicks, are coming soon. Learn more.

Create scalable, event-driven automations with a new user experience for building orchestration rules. This enhancement reduces redundant rules, the time to build advanced orchestrations, and provides a centralized location for minor data cleaning activities. Generally Available for AIOps customers. Learn more.

Our new scheduling system is built on iCal standards (the same foundation as Google and Outlook calendars) to give teams a modern, flexible, and easier to manage experience:

• Quick start templates: Common schedule rotation patterns up and running in minutes
• Multi-responder shifts: Stack coverage when you need it or even add shadow rotations that enable team members to observe shifts without getting paged
• Custom shifts: Build any rotation to fit how your team actually works

Shift-Based Schedules are now rolling out to all customers in Web UI, API*, Mobile App (view + limited overrides), and Terraform. Your existing schedules will continue working and stay fully editable. An upgrade tool is coming soon. Learn more.

Important note: Shift-based schedules use the V3 API and are not compatible with V2 automations. Review this guide to learn more.

This next phase of our transformation includes auto-creation of dedicated incident channels, quick incident declaration to escalate alerts with one click, expanded on-call functionality to page responders directly from Slack, centralized configuration, enhanced responder management to re-open incidents and re-notify team members, and new onboarding tutorials. Available in early access to all PagerDuty customers with Slack integration.

PagerDuty's MCP server expands with new capabilities across Analytics & Reporting and Business Services. Teams can now surface aggregate incident data, service metrics, and team metrics. For Business Services, the release adds business service dependencies, subscriber management, impacted services analysis, and priority mapping. Rounding out the release are two new MCP apps (on our experimental branch): Service Dependency graph and an On-Call compensation report. Learn more here.

Automatically create dedicated Microsoft Teams channels from Incident Workflows. Configure team and channel names dynamically so every incident gets its own communication space. Combine with other workflow actions to build complete MS Teams-based incident response automation. Requires Microsoft Teams integration and Incident Workflows. Available on Business and Enterprise pricing plans. Learn more .

Use the new SRE Agent connectors and tools configuration experience to easily add integrations for the SRE Agent via MCP or API, including connectors to Splunk, New Relic, Honeycomb, Observe, Dynatrace, and more. Available for Early Access to PagerDuty Advance customers. Sign up for early access.

Configure incident workflows to automatically engage the SRE Agent when an incident occurs. The SRE Agent comes to the incident pre-armed with triage data and recommended next steps, reducing the need for escalations and accelerating time to incident resolution. Available for early access for PagerDuty Advance customers. Learn more.

Save time and avoid context switching with a new web-based option for engaging with the SRE Agent. Now responders can kick off agentic triage and response directly from the Incident Details Page. By guiding responders through investigative, triage, and resolution steps, the SRE Agent can help accelerate resolution and reduce unnecessary escalations. Generally available to PagerDuty Advance customers. Learn more.

These new Incident Workflow actions make it easier to automate incident documentation and stakeholder communication. Paired with Scribe Agent, these actions unlock even richer context to accelerate resolution and prevent repeat issues:

• Periodic Incident Progress automatically posts progress updates at a chosen cadence. With Scribe Agent enabled, updates can include meeting transcripts, chat history, and additional incident context. Available for PagerDuty Advance customers only. Learn more.
• Google Meet schedules conference bridges for incidents. Supports adding Scribe Agent to capture audio and chat. Available for all customers; Scribe Agent available for PagerDuty Advance customers only. Learn more.

Start Post-Incident Reviews directly within PagerDuty with incident context built in, with less tool switching and loss of critical details. Coming soon: AI-generated content to help accelerate review completion and team collaboration features to drive follow-through. Sign up for Early Access (requires Professional plan or higher).

PagerDuty Postmortems will reach End of Life on October 31, 2026 for all customers. We're enhancing incident analysis with Post-Incident Reviews in the PagerDuty web UI (in EA), and recommend transitioning from Postmortems to this new, upgraded capability. Existing Postmortem data will be available for download before the EOL date. Learn more.

Configurable from within language settings, the Operations Console is now available translated to Japanese. Generally available to AIOps customers. Learn more.

Save time and avoid context switching with a new web-based option for engaging with the SRE Agent. Now responders can kick off agentic triage and response directly from the Incident Details Page. By guiding responders through investigative, triage, and resolution steps, the SRE Agent can help accelerate resolution and reduce unnecessary escalations. PagerDuty Advance and AIOps customers can now request early access.

Now Generally Available, the SRE Agent can intelligently deduce the next steps for troubleshooting issues by retrieving log data from Splunk, Dynatrace, Elastic, SumoLogic, and knowledge base data from ServiceNow. By guiding responders through investigative, triage and resolution steps, the SRE Agent can help accelerate resolution and reduce unnecessary escalations. Integrate your stack to the SRE Agent today. Learn more.

Access a live, unified view of incidents across services. Quickly identify blast radius, service impact, and detect anomalies by visualizing incidents across time. Service Health Visualization enables faster decision-making and triage at scale by bridging the gap between observability and incident response. Now you can focus troubleshooting in one place with customizable filtering and contextual overlays. Generally available to all customers who have Operations Console. Learn more.

New MCP capabilities provide more flexibility and reduce the tool use back and forth for your incident management. Engineers can now:

• Query by Time: Filter incidents using since and until parameters with relative formats like "last 24h."
• Scale On-Call Queries: Automatic internal pagination now allows quicker and more efficient queries.
• Direct Assignment: Specify an assignee during incident creation to streamline notifications in a single step.

Learn more about PagerDuty MCP here . Want to see what else you can do with MCP? Don’t miss our MCP livestream here .

Improved search experience allows users to find attributes corresponding to incidents, alerts, services, and schedules with enhanced speed and accuracy. This feature leverages advanced indexing and search algorithms to deliver more relevant results quickly. Global Search now includes date range presets, granular time filtering, search alerts by alert key, and more. Learn more here .

PagerDuty for Claude Code brings production context directly into your development workflow. This risk scoring plugin analyzes uncommitted code changes against your incident history. When developers run /risk-score, Claude correlates their git diff with 90 days of PagerDuty incident data—identifying high-risk file types, change scope, and overlap with past incident areas—then delivers a risk score with actionable recommendations before code is committed. Learn more here .

Get full visibility and control over the memory artifacts SRE Agent maintains for each PagerDuty service. With this API, teams can view, edit, or redact information to ensure accurate, compliant, and context‑aware insights that drive faster, more precise incident resolution. Learn more .

Incident Workflows enable you to automate your incident response processes. These workflows can be triggered automatically through Conditional Triggers. The product limits for Conditional Triggers have been increased so that 100 Conditional Triggers (previously 40) can be associated with a given Technical Service and 50 Incident Workflows (previously 20) can have Conditional Triggers that apply to all technical services. Full details on Incident Workflows and Conditional Triggers can be found here.

PagerDuty is launching an MCP plug-in for Cursor. This plug-in allows Cursor to pull in PagerDuty data such as on-call lookups, service management, and more. Not only does this allow developers to resolve incidents faster, it can also help you prevent incidents in the first place, with the crucial information about your operational posture and historical context you need to make the best choice ahead of deploying new code.

Now available in Microsoft Teams, the SRE Agent automatically detects, triages, and diagnoses incidents, and recommends remediation steps. It also recalls incident history to generate playbooks that help prevent recurring issues. The result: shorter incidents, faster fixes, and fewer interruptions. Sign up for Early Access.

Connect PagerDuty to AWS using secure, credential-less authentication that eliminates the need for long-lived access keys. Automate AWS remediation actions through Incident Workflows with enterprise-grade security using AWS-recommended IAM role assumption, reducing the risk of major operational failures while accelerating incident resolution. Available now for all Incident Workflows customers - get started with the setup guide here.

Access a live, unified view of incidents across services. Quickly identify blast radius, service impact, and detect anomalies by visualizing incidents across time. Service Health Visualization enables faster decision-making and triage at scale by bridging the gap between observability and incident response. Now you can focus troubleshooting in one place with customizable filtering and contextual overlays. Early access available to all customers who have Operations Console.

This feature analyzes configured Incident Workflows and evaluates them against the real-time context of each incident. The SRE Agent then intelligently recommends the most relevant workflow to run, ensuring faster, more precise, and context-aware incident response. Sign up for Early Access.

Japanese conversations with SRE Agent in Slack can be enabled via user voice language settings from PagerDuty or via automatic language detection from Slack messages.

The latest MCP enhancements provide richer incident and alert context through expanded capabilities. Engineers can now:

• Retrieve detailed incident log entries with get_incident_log_entries
• Access additional incident data using enhanced query parameters in get_incident
• Inspect alert details using list_alerts_from_incident and get_alert_from_incident

Additionally, list_users now supports including contact method data, enabling responders to reach the right person faster. Learn more about PagerDuty MCP here .

Incident commanders can renotify responders who may have missed the initial alert and cancel pending notifications when circumstances change, directly from the incident timeline. This ensures critical issues never go unnoticed, reducing MTTA/MTTR and preventing service degradation from unattended alerts. Learn more or watch this short demo video.

We've updated our Slack integration with three key improvements:

• New slash commands for quicker access to PagerDuty Incident Management actions.
• Redesigned incident cards with updated emojis and clearer information hierarchy.
• Threaded updates to reduce channel noise. Incident updates now appear as threaded replies by default, keeping your channels organized.

Learn more here.

We are no longer proceeding with the Postmortems End-of-Life that was previously scheduled for January 30, 2026. You can continue using Postmortems.

SRE Agent can intelligently deduce the next steps for troubleshooting issues by retrieving log data from New Relic. Using observability data, the SRE Agent can guide responders through investigative, triage and resolution steps - ultimately reducing MTTR and escalations. Learn more.

Configurable from within language settings, the Operations Console is now available translated to Japanese. Sign up for early access here.

Incident Workflows enable you to automate your incident response processes. These workflows can be triggered automatically through Conditional Triggers. The product limits for Conditional Triggers have been increased so that 40 Conditional Triggers (previously 20) can be associated with a given Technical Service and 20 Incident Workflows (previously 10) can have Conditional Triggers that apply to all technical services. Full details on Incident Workflows and Conditional Triggers can be found here.

When authorized and given an incident ID/URL, service name, or a short symptom description, the PagerDuty Incident Responder agent template, created by LangSmith, pulls incident and service details, correlates recent change events, provides triage information such as past and related incidents, and recommends next steps. Learn more here .

Incident Workflows enable you to automate your incident response processes. These workflows can be triggered automatically through Conditional Triggers. The product limits for Conditional Triggers have been increased so that 20 Conditional Triggers (previously 10) can be associated with a given Technical Service and 10 Incident Workflows (previously 5) can have Conditional Triggers that apply to all technical services. Full details on Incident Workflows and Conditional Triggers can be found here.

Give your organization more control over its AIOps usage. AIOps Service Configuration allows you to disable AIOps on select PagerDuty Services and Event Orchestrations so that only events for teams that are leveraging AIOps features will count against the account event tier. This flexibility provides granular control over AIOps usage and costs, enabling you to apply AIOps to specific business units without incurring event charges for teams not leveraging AIOps. Learn more.

SRE Agent can intelligently deduce the next steps for troubleshooting issues by retrieving log data from observability tools such as Grafana, Datadog and AWS CloudWatch, as well as runbook documents from tools such as Confluence and Github. By analyzing logs and runbooks, SRE Agent can guide responders through investigative, triage and resolution steps - ultimately reducing MTTR and escalations. Learn more.

MCP Change Events management tools allow engineers to retrieve and correlate change events wherever they work. Quickly surface recent changes tied to a failing service or an active incident. Deploy the Docker implementation to standardize access in pipelines, runbooks, and chat workflows so responders can pull the right change context on demand.
Learn more during our upcoming MCP livestream .

Shift from reactive to proactive by leveraging AI Orchestrations to identify actions to automate based on past responder behavior. Using machine learning that has been fed historical event and incident data, AI Orchestrations will suggest actionable Event Orchestration rules to create event-driven automations. Read the KB article, watch the demo, and sign up for Early Access.

Configure the Operations Console to show the incident types and custom fields relevant to you by selecting from a drop down or by using the filter builder. You can also modify the columns to display custom fields by using the column picker. Use this feature to surface your team’s unique metadata so you can have all of the information you need in a single pane of glass to resolve incidents faster. Generally Available to AIOps customers.

Customers using SSO with SAML and a pinned/static PagerDuty SAML signing certificate must update to the new certificate before January 5, 2026 to avoid login failures. Your Account Owner has been sent an email about this on November 4 2025 if your account is impacted by this. The current certificate expires January 5, 2026 and will be removed on December 15, 2025 between 6–7 PM UTC. If your IdP pulls our SAML metadata dynamically (not pinned), no action is required.

Download the End entity and intermediate CA certificate in a single file or End entity certificate . For identification, the new certificate's serial number is 0c1c94a8afa209458553f3c08bf53697 and the old certificate's serial number is031e78b577bc1f4aae7312e07a8b0afb . Learn more about Single Sign-On and SAML with PagerDuty.

Agent-to-agent interaction is here! PagerDuty Advance MCP/API support lets AI agents and assistants securely contact PagerDuty Advance. Teams can access incident context, history, and runbooks from the SRE agent, query the Insights agent for proactive ways to improve, or alter on-call coverage with Shift agent from their AI-enabled platform of choice. Request access here .

Accelerate incident resolution with PagerDuty's forthcoming Azure AI SRE Agent integration, with Early Access planned for December 2025! This prototype agent-to-agent collaboration will allow the Azure SRE Agent to request historic incident context and recommended runbook diagnostic steps from PagerDuty Advance. Sign up for the forthcoming Early Access in December.

Improved resolution forms with system fields that provide better operational insights (e.g. resolution notes, priority, custom fields). Business customers can customize their forms, while Enterprise customers can enforce required fields for compliance and standardization. This structured data collection enables cross-insight learning across the PagerDuty Operations Cloud. Organizations can ensure teams follow standardized processes without relying on individual compliance, while building valuable organizational knowledge. Available on Web, Mobile, and Chat, with more surfaces available soon. Learn more and watch the short demo video.

The PagerDuty MCP server now provides AI assistants and agents access to Status Pages, Incident Workflows, and On-call Management data and actions. These include:

• Status pages: see status pages and status page updates, publish new status page updates
• Incident workflows: list and start incident workflows
• On-call management: create, update, and delete schedules and escalation policies

Want to learn more?Join us for a livestream where we will demo these new capabilities.

Conduct structured, collaborative post-incident reviews that combine incident data with human context to uncover patterns, improve team processes, and drive long-term operational resilience. Teams can trigger Post-Incident Reviews seamlessly from the Incident Detail Page, Workflows, or Slack, making it easier than ever to embed continuous learning into your incident management practice. Enable the feature today through your account settings. Learn more and take the product tour.

Customers can now edit and delete incident notes directly within PagerDuty to maintain accurate incident records. Update notes to correct errors, add missing context, or remove outdated information, reducing time spent on manual workarounds and making post-incident reviews more efficient. Available now for all PagerDuty customers. Learn more or watch this short demo video.

PagerDuty now integrates with Logz.io's RCA Agent to deliver smarter, faster incident resolution. PagerDuty’s integration, once enabled via Incident Workflow action, automatically enriches Logz.io alerts with historical incident context and sends the context back into Logz.io's RCA Agent, which can then complete the root cause analysis and recommend remediation steps. This enables faster MTTR with smarter decision-making, and fewer manual hand-offs. Available for all joint PagerDuty and Logz.io customers.

Want to learn more? Read the blog and join this livestream on November 6 (8AM PST / 11AM EST) to watch a live demo.

PagerDuty’s new homepage is a command center for responders that surfaces the most critical information, like active incidents, on-call schedules, and quick actions. Eliminate context-switching and access everything you need from a single view, reducing MTTR and allowing your team to focus on high-value work. Sign up for early access.

SRE Agent can intelligently deduce the next steps for troubleshooting issues by retrieving log data from observability tools such as Grafana, Datadog and AWS CloudWatch, as well as runbook documents from tools such as Confluence and Github. By analyzing logs and runbooks, SRE Agent can guide responders through investigative, triage and resolution steps - ultimately reducing MTTR and escalations. Sign up for Early Access.

Don’t start triage and response from scratch during critical incidents. The SRE Agent automatically classifies incidents, surfaces critical context from past incidents, and recommends remediation steps. It also learns from your incident history and can generate incident playbooks that help prevent recurring issues. Generally Available in Slack as part of PagerDuty Advance and in Operations Console as part of AIOps and PagerDuty Advance. Learn more.

The PagerDuty MCP server now delivers deeper incident triage and event orchestration details via newly added APIs, enabling AI assistants and agents to access key PagerDuty data including outlier incidents, past incidents, related incidents, and service/global event orchestration configurations. Accelerate the pace of innovation by accessing your incident intelligence and automation logic via AI tools faster. Admins can also use MCP to simplify configuration and validation of AIOps features such as Alert Grouping and Event Orchestration. Want to learn more? Join us for a livestream where we will demo these new capabilities.

This custom agent in GitHub’s AI ecosystem gives users access to PagerDuty data (including change correlation, incident data, and more) directly in GitHub Copilot, saving time from context switching for faster resolution. The agent can help users analyze incident context, identify recent code changes, and suggest fixes via GitHub PRs. Learn more about PagerDuty’s MCP capabilities for GitHub and other tools here .

Now that the PagerDuty plugin for Backstage also supports Spotify Portal, you can embed incident management capabilities directly into your Spotify developer portals, helping to eliminate context switching that slows incident response. View active incidents, check on-call schedules, trigger incidents, and map service dependencies without leaving your Spotify Portal environment. The plugin includes automated service mapping with bidirectional sync so you can choose PagerDuty or Spotify Portal as your source of truth for service topology. By embedding PagerDuty into Spotify Portal, consolidate your operational stack to a single interface, accelerating developer velocity and enhancing operational excellence. Available now for all PagerDuty customers. Read the launch blog to learn more. Get started with documentation.

Unlock the power of your operational data directly from Slack. Available for all PagerDuty Advance customers, Insights Agent offers proactive recommendations and on-demand insights based on Incidents, Services, and Teams Analytics. By surfacing risks, trends and optimization opportunities with no toil, this AI agent empowers teams to build more resilient operations and get ahead of potential issues. Take the interactive Product Tour and watch the demo.

We’ve launched over 150+ platform enhancements and updates, plus announced AI innovations and new and improved integrations. Check out what you can expect to see starting today and extending across the next two quarters.

End-to-end Incident Management

We’ve introduced over 150 customer-driven updates to make incident management more flexible and adaptable to your workflows. Additionally, we’ve announced new features including Flexible Shifts (forthcoming EA) for simplified, recurring on-call scheduling, Shift Agent (GA) for managing conflicts and overrides directly in chat, and enhancements such as Required Fields on Resolve (EA), Reopen Incidents (GA), Renotify Responders (forthcoming), and Add Attachment to Incidents (EA).

Purpose-built AI-powered Operations

This release expands automation and AI capabilities across the incident lifecycle with new and enhanced AI agents designed to accelerate response and reduce manual effort. Scribe Agent (GA), SRE Agent (EA), and Insights Agent (EA) provide automated call transcriptions, smart summaries, support for triage and remediation, and proactive recommendations. AI Orchestrations (forthcoming EA) further enable proactive incident response through machine learning-driven recommendations.

Integrated Developer Experiences

We’re embedding PagerDuty more deeply into your existing tools and workflows. The MCP Server (GA) now supports both remote and local connections to AI toolkits and IDEs, while the enhanced Backstage integration (GA) offers deeper insights. Chat-native experiences are also being enhanced in both Slack (GA) and Microsoft Teams (forthcoming EA) with AI-first workflows and easier onboarding.

Please see our table of all 150 changes below:

Improvements:

• Service graph navigation improvements via service dependencies

• Operations Console: Date filter now shows current time

• Service Dependencies: Manage Service Dependencies directly navigates to the Service Dependency page

• Rundeck: Job Export: Added creation date to API response

• Analytics: Added Escalation Policy filter to Responders report

• Mobile App: Updated Download Mobile App header

• User Onboarding: Real-time report update status

• PagerDuty Advance: Analytics Dashboard provides visibility into expired credits

• PagerDuty Advance: Navigation bar improvements

• PagerDuty Advance: Expired trials analytics support

• PagerDuty Advance: Updated trial expiration page

• PagerDuty Advance: Improved Japanese language support

• PagerDuty Advance: PagerDuty proactive insights on Slack only showed to AIOps accounts

• Scribe Agent: Updated Scribe card with meeting participants

• Scribe Agent: Improved configuration settings

• Scribe Agent: Added meeting participants to Scribe Agent summary

• Scribe Agent: Add participant tracking to Scribe output

• PagerDuty Advance: Improved unclear request handling

• PagerDuty Advance: show availability of agents on different surfaces

• PagerDuty Advance: Improved integration prerequisites that prevent users from enabling Slack or MS Teams as a surface unless the integration has already been set up

• PagerDuty Advance: Dynamic next step suggestions

• PagerDuty Advance: Added Change Event URLs to Slack/Microsoft Teams cards

• PagerDuty Advance: Amazon Q button only displayed when connected to account

• PagerDuty Advance: ability to send the 'timezone' field from Microsoft Teams

• PagerDuty Advance: Use user timezone to convert dates in response

• Service Creation: Enhanced Accessibility

• Event Orchestration: Enhanced Rule Creation form with Improved Accessibility

• Event Orchestration: Consistent Dynamic Routing Behavior Across Service Name and ID

• International SMS: Prevent duplicate international requests

• User Profile: Added URL routing

• Admin: SMS verification skip controls

• China Phone Numbers: Removed SMS verification requirement

• Geolocation API: Added verification status

• Push Notifications: Added contact method index number for duplicate names

• Conference Bridge: Improved voicemail clarity

• Schedule Overrides: Improved page navigation behavior

• OCHON Emails: Readability improvements

• Mobile App (Android): Push notification contact method limits warning due to many contact methods

• Mobile App (Android): Detect Missing Device Registration

• Mobile App (Android): Push notification status warnings

• Mobile App (iOS): Push notification status warnings

• Mobile App (iOS): Improved notification troubleshooting

• Post-Incident Reviews: Added Incident ID column

• Post-Incident Reviews: Jeli updated to PagerDuty brand colors

• Insights Agent: Reduced repetition in response output

• Insights Agent: Improved Time-Based Metric Output Formatting

• Insights Agent: Improved agent response accuracy and consistency

• Insights Agent: Improved Insights Agent Output Format

• ServiceNow Integration: Redesigned integration health-check page for clearer status visibility and easier troubleshooting

• Status Pages: UI/UX improvements to page history and posts

• Jira Cloud Integration: Dark theme support

• Analytics: Add Escalation Policy column to Responders report

• Post-incident-reviews: improve error message when user does not have permissions to view opportunity

• Scribe Agent: Improve card output after meeting ends

  • Scribe Agent: Add /pd scribe command to slash command help menu

Enhancements:

• Operations Console: Timeline support in side panel

• Operations Console: Ability to create incidents directly from the Console

• Service Enable/Disable Audit Trail reporting

• Operations Console: expanded the allowed interval for creating filters from 31 to 61 days

• Rundeck: Added log4j2 configs for preauthentication to all default templates

• Analytics: New Ack Rate Charts

• Analytics Dashboard: Added chart drill-down capability

• Event Orchestration: Added Page Titles for Better Navigation

• Contact Methods: Modern redesign

• Notification Rules: Streamlined interface

• Admin: SMS verification override capability

• New User Profile Tab

• User Profile: Feature toggle support

• Post-Incident Reviews: Incident status updates now shown in PIR narrative evidence

• Post-Incident Reviews: Custom field changes now shown in PIR narrative evidence

• Post-Incident Reviews: PagerDuty incident ID displayed more prominently in Post-Incident Reviews

• Jira Cloud Integration: Enable/Disable Configurations via API

• Jira Cloud Integration: Remember Configurations table preferences and pagination

• Jira Cloud Integration: Bulk JQL validation for configurations

• Jira Server Integration: Dark theme support for Jira Server version 10+

• Status Pages: Auto-refresh functionality to keep the open status page up-to-date

• Jira Server Integration: Personal Access Token support for Jira Server

• Status Pages: Ability to set Publish Time for Post creation and updates

• Jira Cloud Integration: Added Incident Reopen support

• Jira Cloud Integration: JQL validation on Configuration New/Edit form

• Jira Cloud Integration: Ability to Enable/Disable Configurations

• Slack: Extended threading in dedicated incident channels

• Slack: Added embedded responder links

• Slack: Added customizable notification detail levels

• Slack: Remove redundant information in Dedicated Channels notifications

• Slack: Enhanced API bot token fallback to support automation without requiring individual PagerDuty-Slack user account linking

  • PD Advance Agents: Japanese support to RAG, Shift and Insights Agent

Performance:

• Web-app performance improvements for all pages

• Service listing performance improvements across pages

• Improved performance loading service dependencies

• PagerDuty Advance: Faster channel summarization

• Schedules: Page load time improvements

• Schedules API: Performance improvements

• Teams Page: Improved performance of escalation policies tab

• Teams Page: Improved performance of services tab

• Incidents Page: Improved performance of incident timeline

• Account Page: Improved performance of /account/incident_priorities

• AIOPs: Latency improvement for recent changes and probable origin

  • Status Pages: Improved automated incidents performance

Accessibility:

• Teams Page: Enhanced accessibility of escalation policies tab

• Teams Page: Enhanced accessibility of services tab

• Incidents Page: Enhanced accessibility of incident timeline

• Account Page: Enhanced accessibility of /account/incident_priorities

Bug Fixes:

• Fixed: Intermittent error when changing impacted service

• Global search: fixed indexing issue with incident notes

• Service Dependencies page: Fixed 'Try our API' link

• Operations Console: Fixed service name search inconsistency

• Rundeck: Project export: Fixed select/deselect all functionality

• Rundeck: Fixed project export in version 5.14.1

• PagerDuty Advance: Credit Breakdown Chart shows Total Credits Used

• Analytics: Fixed Service Uptime chart display

• Analytics: Team drilldown for unassociated teams

• Account setup completion banner does not dissappear after complete.

• Incident Activity data consistency between UI and CSV

• Fixed: Weekly Analytics email delivery

• Analytics: Fixed: Responders do not respect filter settings

• Analytics: fixed issue with respecting user permissions in insights

• Trial Onboarding: Fixed modal display after integration skip

• User Report (UI): Fixed error Code 429 with user Salesforce

• User Report (UI): Fixed teams dropdown duplicate text and behavior

• Fixed country code selection not behaving correctly during onboarding

• Analytics: Fixed timezone handling issue in User Report

• PagerDuty Advance: Fixed Agent Console UI to show the correct number of used credits

• Conference Bridge: Fixed One-Touch Join feature inconsistent bevahiour

• Schedules: Fixed DST midnight timezone display

• Fixed: Incident timeline displays incorrect responder info when multiple targets

• Fixed overrides not being removed for inactive users

• Post-Incident Reviews: Fixed Jira ticket addition to Post-Incident Reviews

• Shift Agent: Fixed team schedule lookup

• Shift Agent: Improved query matching accuracy

• Shift Agent: Fixed multi-team on-call information

• Shift Agent: Fixed last shifts follow up routing

• PagerDuty Advance Agent: Fixed general question routing

• Shift Agent: Improved service name matching

• Insights Agent: Improved MTTx calculations of multiple services/teams

• Shift Agent: Inaccurate answer for oncall shifts for team

• Event Transformer documentation link broken on app registration

• AIOPs: Consistency improvements to matching logic

• Status Pages: Better date/time selection validation for scheduled maintenance

• Salesforce Integration: Support disable/enable triggers on Case object

• Status Pages: Fixed "All External Status Page" breadcrumb navigation in Template creation/edit form

• Salesforce Integration: Resolved broken "Go to PagerDuty" link

• Status Pages: Fixed audience settings fetch

• Status Pages: Fixed post update review flow when post does not exist

• Status Pages: Fixed post update form to respect saved value for notifications checkbox

• Status Pages: Fixed maintenance post ordering by start date

• Zendesk: Fixed urgency mapping

  • Salesforce Integration: Resolved configuration summary showing 'Webhook Not Connected'

Text/Copy Improvements:

• Scribe Agent: Improved Scribe Agent card copy

• Add "Message frequency varies." copy to registering Contact method

  • Post-Incident Reviews: Renamed “Opportunity” to “Post-Incident Review” Across Jeli and PagerDuty Surfaces

PagerDuty's new Slack Work Objects integration brings critical context and actionable incident details directly into Slack, keeping your team focused and responsive without ever leaving their conversation flow. Rich, metadata-powered previews and persistent side panels provide real-time incident status and management capabilities with secure, authenticated access to sensitive data. By centralizing incident response within Slack, teams respond faster and collaborate more effectively. Available for all customers using the Slack integration.

Don’t start triage and response from scratch during critical incidents. Available within Slack and the Operations Console, the SRE Agent automatically classifies incidents, surfaces critical context from past incidents, and recommends remediation steps. It also learns from your incident history and can generate incident playbooks that help prevent recurring issues. Available for Early Access in Slack for AIOps and Event Intelligence / Digital Operations customers—sign up here.

Reactivate resolved incidents directly from PagerDuty while preserving all context, notes, and history. Teams can assign reopened incidents to users or escalation policies, maintaining proper notification flows and reducing operational overhead by eliminating the need to create duplicate incidents. Please note: Integration behaviors vary by ITSM/CSM system - reopening incidents in ServiceNow creates separate new PagerDuty incidents, while Jira support varies by version. Generally available to all customers on the Incident Details Page, with Chat and Mobile coming soon. Learn more.

Generally available for PagerDuty Advance customers, this AI-powered solution streamlines on-call management through intelligent conflict resolution based on PagerDuty Schedules and/or Google Calendar data. Directly from Slack, the Shift Agent can:

• Share on-call schedules and upcoming shifts
• Automatically detect PTO conflicts
• Recommend available team members for shift coverage and message them to facilitate the override

This reduces manual scheduling work, and ensures seamless on-call coverage—all while saving valuable time for more strategic work. Take the interactive Product Tour and learn more here.

The Scribe Agent automatically delivers real-time transcription of Zoom calls to your Slack incident channel, and a smart summary with key topics and action items. You can add Scribe Agent to any incident-related conference bridges via your account’s AI Settings or as an Incident Workflow action. This helps ensure teams don’t miss critical information during incidents while remaining focused on resolution.

Take this interactive Product Tour and learn more here.

We're updating the Downloaded Mobile App column name to Has Mobile App and Notifications Enabled, in the User Onboarding Report, to better reflect the logic behind the column values more accurately and allude to what the data actually measures. This eliminates confusion and brings more clarity in the adoption of the Mobile app and push notifications by users. Available September 22nd, 2025. [Learn more]

The PagerDuty ServiceNow ITSM integration now supports OAuth (Client Credentials) as an alternative to Basic Authentication for webhooks. Customers can select the authentication method that best fits their security and compliance needs, helping organizations in regulated industries meet requirements and align with modern standards. Learn more.

Transform your incident resolution workflow by customizing which fields appear when resolving incidents. Select from your incident type's custom fields, inherited fields from base types, and system fields like priority to create tailored resolve forms. Enterprise customers can mark fields as required and reorder them for optimal workflow. Available on Web (Mobile and Chat support coming soon). Sign up for early access.

Automatically or manually create Jira issues during incidents with configurable conditional triggers in PagerDuty Incident Workflows, eliminating manual creation and tab switching. Teams can now ensure consistent, structured Jira issue creation for incidents as needed while reducing toil during critical response and improving post-incident visibility. Set up your automated workflows today [link] Learn more.

Securely share real-time service status updates with internal employees, partners, or VIP customers using Private or Audience-Specific Status Pages, gated by SSO (OpenID) authentication. Teams can now provide targeted, transparent communication while protecting sensitive operational information, reducing support ticket volume and building customer trust. Learn more.

Allow any Slack user to create incidents directly from chat without requiring PagerDuty accounts or profile linking. This reduces time to resolution and prevents minor issues from escalating into major operational failures. Maintain security through admin-controlled service allowlists that determine which services are available for incident creation. Learn more.

PagerDuty is enhancing incident analysis capabilities by upgrading from Postmortems to Post-Incident Reviews. US service region customers can start using Post-Incident Reviews to get better insights and start learning from incidents. You can continue to use Postmortems until January 30, 2026. Existing Postmortem reports will be automatically converted to opportunities within Post-Incident Reviews on January 30, 2026. Learn more and take the product tour.

Unlock the power of your operational data directly from Slack. The Insights Agent delivers proactive recommendations and on-demand conversational insights based on your Incidents, Services, and Teams analytics. By effortlessly surfacing operational risks, trends and patterns, this AI agent empowers data-driven decision making to build more resilient operations. Sign up for Early Access here!

Want to learn more? Join this live webinar to discover the full roster of PagerDuty AI Agents built to boost team productivity, reduce burnout, and streamline operations—plus, get an exclusive sneak peek at our upcoming SRE Agent.

The PagerDuty Advance integration with Amazon Q Business index enables quick access to critical data from across your Amazon Q Business connected apps like Confluence or GitHub. Boost operational efficiency and accelerate incident resolution by surfacing key enterprise knowledge in Slack or Microsoft Teams, without manual toil or context switching.

Generally available to PagerDuty Advance customers. Learn more here.

The Scribe Agent automatically transcribes your Zoom calls in real-time and delivers the transcripts to Slack, including a summary of key discussion topics and action items. This ensures teams can capture critical information and document their shared knowledge without disrupting their workflow. Sign up for Early Access here .

Conduct structured, collaborative post-incident reviews that combine incident data with human context to uncover patterns, improve team processes, and drive long-term operational resilience. Teams can trigger Post-Incident Reviews seamlessly from the Incident Detail Page, Workflows, or Slack, making it easier than ever to embed continuous learning into your incident management practice. Available now for Professional, Business, and Enterprise Incident Management (EIM) plan customers in the US region – enable the feature today through your account settings. Learn more.

As part of our new incident management plans announced earlier this year, Business plan customers can now assign specific team members or escalation policies to this new custom role during incidents, standardizing and adding structure to their incident management. Generally available for Business plan customers. Learn more.

Create scalable, event-driven automations with a new user experience for building orchestration rules. This enhancement reduces redundant rules, the time to build advanced orchestrations, and provides a centralized location for minor data cleaning activities. Learn more.

Without leaving Slack, users can instantly access critical data from Amazon Q Business connected apps like Confluence or GitHub. This improves operational efficiency and accelerates incident resolution by surfacing key enterprise knowledge without manual toil or context switching.

This new capability builds upon the existing functionality to take PagerDuty actions directly from Amazon Q Business. Early access to integrate Amazon Q Business is open to PagerDuty Advance customers—sign up here.

Get intelligent, stress-free on-call conflict resolution with the Shift Agent. In Slack, share any planned time off with the agent to quickly surface potential conflicts with upcoming shifts. Prompt the agent to list who is available to take those shifts, ensuring seamless coverage without the manual toil. Sign up for Early Access here.

Customers get a more flexible incident response by being able to trigger incident workflows directly from single-select custom fields that matter most to their organization. This unlocks the ability to further automate and tailor incident response to their specific processes. Available for Business and Enterprise customers. Learn more.

Easily move incidents across services with minimal clicks, from the incident’s web detail page, in Microsoft Teams and Slack, in Operations Console, on mobile, or via the ServiceNow 8.2 integration. The result? Streamlined triage, faster resolution, and more accurate metrics for enhanced operational insights. Learn more.

Build more flexible automation with Automation Actions by using context variables to reference incident custom fields as parameters within your scripts or as job options for RBA Jobs. Teams can now reference data from alerts via custom incident fields to configure and invoke more specific diagnostics and remediation. Reduce overall operating costs with intelligent automation that minimizes manual intervention and streamlines incident remediation to induce time for more value-add work. Generally Available in Automation Actions. For more information on Automation Actions and context variables for Incident Custom Fields, check out our docs.

Teams can now set or change an incident’s type using the new “Update Incident Type” action in incident workflows. This means incidents are always classified correctly and routed to the right response process (like “Major Incident” or “Security Incident”). Available for Business and Enterprise customers. Learn more.

Achieve seamless operational workflows across systems, improve incident context, and accelerate resolution by connecting tools across your incident management tech stack with standardized service metadata. Automatically populate important service information such as criticality, business and technical owners, and configuration details using the Service Custom Fields API and Terraform. Now in Early Access for Incident Management customers on Business or Enterprise plans.

With Intune support for Mobile, customers can more securely manage the PagerDuty Mobile app while improving compliance with regulations and policies. Intune’s Mobile App Management (MAM) capabilities allow organizations to enforce policies like blocking copy/paste between unmanaged apps, encrypting data, remotely wiping devices, and more. This helps organizations protect revenue by reducing data breach risks and improving compliance. Available for Enterprise Incident Management (EIM) customers. Learn more.

Manage and differentiate security incidents with the new Security Incident Type. Classify and respond to security events with tailored workflows, custom fields, and enhanced reporting. Teams can now ensure security incidents are handled with the right process and visibility, reducing the risk and cost of major operational failures. Learn more.

Trigger automated remediation at the alert level to prevent incidents from being created in the first place. Reduce responder intervention, minimize customer impact, and free up teams for higher-value work. Generally Available to AIOps and AIOps + Runbook Automation customers. Learn more.

We're excited to announce 4 new workflow actions (Get Business Service Details, Get Users on a Team, Get Alerts for an Incident, and Get User) that streamline incident management by automatically gathering and integrating critical information. These actions let you retrieve business service details, team members, alerts, and user information—while also enabling you to push this data to external services, dashboards, and Slack. Reduce manual coordination and customize data flow to match your team's needs. Available now for all Business and Enterprise plans.

Accelerate your incident response with a newly streamlined incident submission form. When triggering an incident from Slack or Microsoft Teams, our updated experience only asks for the required fields so you can get started quickly, while giving you the flexibility to add details such as Urgency and Priority when needed. Available now for all customers.

Enhance your incident response with a new way to capture and reference critical details directly in your chat channels. Responders can view and update all custom field types in dedicated Slack incident channels or Microsoft Teams incident chats, making incident collaboration smoother and faster. Available now for Business and Enterprise customers. Learn more in our Slack and Microsoft Teams user guides.

Round Robin orders will no longer restart when editing an escalation policy. The on-call sequence remains unchanged, ensuring a predictable and equitable process that streamlines operations and reduces unnecessary work.

Build more dynamic orchestrations using variables that leverage data from incidents and external systems via API to cover a more diverse set of automation use cases. Teams can initiate actions based on existing automation outputs, such as suppressing unnecessary future incidents when the diagnostics results indicate the issue has been resolved, reducing the total cost of operations, and freeing up time for value-add work such as R&D. Learn more.

Slack users can now engage with the PagerDuty Advance AI Assistant via direct message within Slack's side panel. Get context-aware responses that intelligently reference incident details from the Slack channels you are viewing, in a single, private thread with PagerDuty Advance. This minimizes context-switching and reduces operating costs by enabling more efficient workflows and focused problem-solving through automated, contextual interactions. To enable this feature, PagerDuty Admins need to reauthorize the Slack Integration. Available for PagerDuty Advance users with a Slack paid plan. Learn more.

The Operations Console allows teams to take action on time-critical incidents from a shared, centralized command center, minimizing business impact, and protecting customer experience. With the latest enhancements, responders can access key contextual information from the side panel at a glance, take actions on alerts (merge/unmerge), enrich their workflows with Custom Fields, and utilize improved filtering for faster data navigation, reducing operational costs and protecting customer experience. Learn more.

Easily move incidents across services with minimal clicks, from the incident’s web detail page. The result? Streamlined triage, faster resolution, and accurate metrics for enhanced operational insights. Watch it in action in this demo.

PagerDuty can now notify users of incidents and add responder requests via phone call. Users will have the option to select their preferred language to receive notifications. To change your language, see this knowledge base article for more information.