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.

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.