Platform Release Notes (2022)

December 2022

Product limit: Email subject line truncation
This change truncates reminder email subject lines to 250 characters or less. This will affect on-call reminders, incident alerts, and add responder requests. For any questions, please reach out to [email protected].

New mobile login experience
The login experience will begin with requiring you to enter your email address. Your email address will then drive the rest of the login experience, presenting the you with more streamlined and relevant options at every step. If you have additional questions, please contact [email protected].

Easier Allow-list Subdomain User Experience
Account Owners will be able to quickly change the behavior of the Email Domain Allow List in the Email Domain Restriction section. The new experience consists of the addition of an “Allow Subdomains” check box on the Account Settings page -- it will be unchecked by default. This default maintains the current functionality, which requires explicit enumeration of every sub-domain that needs to be allowed in the Email Domain Allow List. When the check box is checked however, only top level domains need be specified in the Allow List, and the sub-domains below them are automatically inferred. Please contact [email protected] if you have additional questions.

Generic Webhooks v2 EoL extension
Previously we had communicated that generic webhooks v2 would be deprecated at the end of March 2023. We have decided to postpone that date until further notice. It is important to remember that: 1. The end-of-support date that we initially communicated (October 2022) is still valid. This means that we no longer accept any new features requests for webhooks v2. 2. This extension does not apply to specific integrations (e.g. Slack) that have their own end-of-life schedule. Please refer to this page for more information about Webhooks. If you have additional questions please contact [email protected].

November 2022

The general availability of New Mobile Home Screen - November 14, 2022
The new PagerDuty Mobile Home Screen Experience puts "my open incidents" front and center, so the top recent incidents and related details are easily seen. Responders who want a broader awareness of digital operations can easily access non-incident information like on-call shifts and impacted technical services. This is just the latest in a series of new mobile app enhancements we've rolled out this year. You can learn more by reading knowledge base article.

New product limit as of October 25, 2022: Max # Schedule Layers
The incident response product team is introducing a patch to a previously created product limit to our Schedule API. The Schedule API will no longer allow customers to add Schedules with more than 60 layers. Schedules that already have 60 layers will continue to be editable via the API as long as those updates do not increase the number of layers. This will not affect most customers. If you have any questions, please reach out to [email protected].

Expanded Incident Response Functionality in Microsoft Teams
Starting 11/9/2022 incident responders will soon be able to perform additional incident management actions from MSFT Teams, including: changing priority, reassigning, adding responders, escalating, and performing PagerDuty Automation Actions. You can read more about this features in this blog. If you have any questions, please reach out to [email protected].

Sign up for Incident Workflows Early Access
Use a no-code/low-code builder to create customizable incident workflows that will reduce the manual work required to escalate, mobilize, and orchestrate the right incident response for any use case. Automatically trigger an orchestrated response using if-this-then-that logic to sequence common incident actions, such as adding a responder, subscribing stakeholders, or starting a conference bridge. To learn more, check out our KB article and sign up for Early Access.

Product Launch

Everyone wants fewer incidents, faster resolution, and better customer experiences. But how can you get there? And soon. As the market leader on end-to-end incident response, we’ve released a new set of capabilities to help you do so.

Watch the webinar replay anytime for a deep-dive into these new updates, like:

  • Incident Workflows: Automate a series of steps during incidents (like setting up a Slack channel and notifying stakeholders), so responders don’t have to do it manually.
  • Status Pages and Notification Templates: Proactively communicate standardized operational updates to specific audiences in real time.
  • Flexible Time Windows for Intelligent Alert Grouping: Get more precision and greater flexibility when tuning out system noise during selected times.
  • Incident Response Ops Guide: We’ve collected our own learnings from years of incident reviews and process refinement in this refreshed reference guide.

Let us know if you’re interested in joining our Early Access Program.

October 2022

Status Update Notification Templates latest updates now early access!
With organization-based templates, companies can now customize and standardize communications based on impact, service areas, and more. This functionality will be also available via API, so teams are able to customize and leverage status update notification templates to fit their needs in any tool or context. To be added to our early access list, please fill out this form.

The newest version of our Salesforce application is now available
PagerDuty's latest version of our Salesforce application, v3.7 is now available. Some benefits of this latest versions are:

  • Webhook Extension upgrade to PagerDuty webhooks v3 - This upgrade allows extensions to be added at the account level instead of the service level with webhooks v2
  • New Salesforce Extension page and the ability to see what Salesforce accounts are connected to PagerDuty
    -Default Object mapping for the salesforce incident object with the standard integration
    -The ability to select if rulest actions should be limited to PagerDuty or Salesforce objects created as part of the ruleset flow.

Visit our Salesforce integration guide for more details. If you have additional questions, please reach out to [email protected].

Operational Updates to Event Orchestration
Based on customer feedback, we’re launching updates to Event Orchestration to aid in overall ease of use, including:

  • Recent event view now includes the ability to select json payload objects and have them converted to EO rule conditions
  • Orchestration will aggregate all prior applicable rules for the selected rule, summarizing the relevant conditions as well as the actions that will be applied to ingested events
  • Page names will be standardized to better align with nomenclature in PagerDuty Knowledge Base

Product Notice: Event Rules EOL Delayed to April 2023
To give our customers more time to plan their migrations to Event Orchestration, we are delaying the End-of-Life for the Event Rules feature to April 2023. When this happens, we will auto-migrate any Event Rules over into Event Orchestrations, one-to-one. Learn More

Check out PagerDuty's new seamless solution for Automated Diagnostics for AWS
We just launched Automated Diagnostics for AWS in PagerDuty to help our customers quickly triage problems in AWS environments. This soliution consists of a seamless integration of Automation Actions and Runbook Automation connected to PagerDuty Incident Response and PagerDuty Event Orchesration. It provides prebuilt common diagnostics for frequently used AWS services, and an easy way to add your own diagnostics. Learn about the new solution here

Updates to the PagerDuty Admin Experience Coming Soon
We have created a new experience for the user and subscription management pages. Account admins will now be able to quickly understand which licenses each user has been assigned and how many licenses of each license type have been deployed. You will see the following changes:
• The Users List page will be the place where you manage user licenses.
• Role assignment will no longer be available from the Individual User Details page.
• On the Subscription Management page, the plan details and billing summary will show multiple base licenses where applicable.

Your existing license assignments will not change. All corresponding updates to our APIs will be documented here. We will roll out these changes gradually over the next 2 months. If you have additional questions, please contact [email protected].

September 2022

v1 Webhooks EoL (End of Life) is next month
This is a follow-up reminder to previous communications. The End of Life date for v1 Webhooks is 10/31/2022. This means:
• You won’t be able to create new v1 Webhooks or use existing connections to v1 Webook extensions.
• Apps or integrations that are using v1 webhooks will stop working.
For more details and steps to migrate to v3 Webhooks please refer to this page. If you have additional questions, please reach out to [email protected].

New! Create and manage maintenance windows through PagerDuty Mobile App
Maintenance Windows feature for PagerDuty mobile app is generally available starting September 15th, 2022. Maintenance windows temporarily disables a service, including all its integrations, for a set period of time while it is in maintenance mode. Now, users away from their desk or office have the flexibility to create, update and delete maintenance windows through PagerDuty mobile app. You can learn more about the mobile maintenance window through Knowledge Base Articles or try it out by downloading iOS or Android.

PagerDuty Process Automation 4.6.0 & Rundeck Community 4.6.0 is released
Check out the new features and enhancements for PagerDuty Process Automation (formerly Rundeck Enterprise) and PagerDuty Runbook Automation and Rundeck Community included in this release. This release includes a new plugin for AWS Athena that job definitions to include SQL queries against Amazon S3, an enhancement of the Amazon ECS node source plugin to handle multiple clusters within the same region, and a number of security and compliance updates, and bug fixes.

View our Twitch stream review of this release live on Tuesday, Sept 13, at 10AM Pacific.

View the release notes here.

August 2022

New Mobile Service Maintenance Window - Early Access
We will gradually release the new PagerDuty Mobile Maintenance Window for Early Access starting on August 23, 2022. The release of the mobile maintenance windows temporarily disables a service, including all its integrations, for a set period of time while it is in maintenance mode. Now, users away from their desk or office have the flexibility to create, update and delete maintenance windows through PagerDuty Mobile App. You can learn more about the mobile maintenance window through Knowledge Base Articles or try it out by downloading iOS or Android.

New option to display PagerDuty on the sidebar for relevant projects for Jira Cloud customers, available in September.

  • For new Jira Cloud customers, PagerDuty will not be displayed by default on the sidebar of all Jira Projects.
  • For existing Jira Cloud customers, JIRA project admins will have the ability to hide or display PagerDuty on the Jira sidebar per project.
  • If you have any questions, please reach out to your PagerDuty account team or Customer Support ([email protected]).

Annual marketplace app re-certification for Jira Data Center Integrations
We have officially re-certified our Jira DC (Data Center) integrations for another year, maintaining our DC Approved Status in the Atlassian marketplace.

Remedy Integration ownership transferred to KTSL
PagerDuty has handed the Remedy integration to a partner called KTSL who will take it over going forward. The integration is now built and supported by KTSL as outlined here.

New components now available on
We have added several new components for customers to subscribe to on Existing subscriptions will remain intact. These new components include:

  • Incident Timeline and Alert Logs
  • Services
  • Schedules and Escalation Policies
  • Users and Teams
  • Change Events
  • Business Services/Status Dashboard
  • Account Settings

PagerDuty App update in Salesforce appexchange.
There is a minor update to our PagerDuty App in the Salesforce app exchange that improves the PagerDuty logs page with date filters as well as the logs that needed to be deleted thorough the delete interval on the on the PagerDuty configuration page.

Product Notice: Event Rules will EOL and migrate to Event Orchestration in January 2023
In order to deliver a robust and reliable experience for our customers, we will End-of-Life the Event Rules feature in January 2023. Don’t worry: In support of this EOL, we will auto-migrate any Event Rules you are using over as Event Orchestrations, one-to-one. From then on, you’ll be able to do everything in Event Orchestration that you can in Event Rules today. To learn more, visit PagerDuty's knowledge base or contact your account manager.

New Default iOS Notification Tone for “Add Responder” Requests
Starting on August 2, 2022 the iOS notification tone for “add responder” requests will change to make it more distinguishable from non-PagerDuty notifications. Previously, responder requests used the default iOS notification tone, but with this update, responder requests will use the “PagerDuty Alert” noise. If you have any questions, please reach out to your PagerDuty account team or Customer Support.

Empowering Customer Service Agents with Automation
PagerDuty Automation Actions is now available within the PagerDuty application in Zendesk. With Automation Actions, agents can automatically validate problems and capture critical information instantly for the team to diagnose and resolve. Agents are empowered to validate customer-impacting issues and run automation actions directly from the PagerDuty app in Zendesk. To learn more, visit PagerDuty's knowledge base or contact your account manager.

Restricted Access Users can now manage Webhooks V3 for their teams
Restricted Access Users with a Manager Team Role, will now be able to manage Webhooks V3 integrations for their team(s). The operations team will no longer depend on Global Admins and Account Owners to manage its day-to-day operations.

July 2022

Service Standards now generally available to all customers
Use Service Standards to improve operational maturity and provide a better customer experience by establishing criteria that standardizes what ‘good’ looks like across teams. Configure services according to best practices and scale service ownership across the entire organization. To learn more, check out the Knowledge Base article or watch the webinar on-demand.

June 2022

PagerDuty for Google Chat is now available
PagerDuty for Google Chat was built by Google in tight collaboration with PagerDuty. PagerDuty for Google Chat enables incident responders to get notified, initiate resolution, and focus on the problem at hand without switching context from your Google Space. Learn more about PagerDuty for Google Chat by reading our integration page.

The new minimum OS requirement for PagerDuty mobile app
We are introducing the new minimum OS requirements for PagerDuty mobile. The future versions of PagerDuty mobile app will require Android 9.0 and iOS 14.0 or later. This minimum change is to ensure our mobile users are getting:

  1. Better data security for PagerDuty mobile
  2. New and better mobile experiences on the latest operating system
  3. Latest innovation by taking advantage of the most up-to-date devices and their capabilities. Please ensure your device is upgraded to the continue receiving mobile app updates.

PagerDuty Summit
We hope you could join us last week for PagerDuty Summit to hear about all of our product announcements. If you'd like to check out any of our sessions, or read deeper into our product announcements check out:

  • Our launch blog with details on the highlights of the launch.
  • Replays of all of our Summit sessions - keynotes, customer sessions, and product deep-dives.
  • Our What's New page where you can see the launch details at a glance and express interest in participating in early access.

Restricted Access Users with manager permissions can now manage their Slack channel connections
PagerDuty customers on Next Generation Slack V2 on Webhooks V3 using the Restricted Access User (RAU) role with manager permissions can now manage their Slack channel connections. The Slack connection management page is accessible via the service page integration tab. When viewing that page, users will see all connections, but will only be able to edit the ones for which they have permission.

Customer Service Operations Release Notes


Release notes for Version 3.6 of the PagerDuty for Salesforce service cloud application in Salesforce appexchange.

  • The ability to Edit incident details - Title and Priority, from the incident command console
  • The ability to view the information for a conference bridge and Join from the incident command console
  • The ability to Run an Automation Action from the incident command console
  • The ability to select an Automation Action as a ruleset action when creating a rule in Salesforce
  • The ability to view the output report for an automation action from the incident command console
  • The ability to schedule log delete duration between 1 and 90 days. The default duration remains 60 days.
  • Hard delete for PagerDuty logs. Logs will no longer be stored after they are deleted.
  • Reduced future Apex usage for rulesets processing. Future jobs will be scheduled for just events that match the rule conditions where there are rule actions to execute - each job will be processed individually.
  • Increase in log processing time out time from 30 seconds to 120 seconds.

For more details, please read the Salesforce Service Desk Integration Guide.


Release notes for the PagerDuty application in Zendesk Marketplace

The ability to Edit incident details - Title and Priority, from the incident command console
The ability to view the information for a conference bridge and Join from the incident command console
The ability to view technical Incident details in the Status dashboard
The ability to subscribe to technical incident details from the status dashboard

For more details, please read the Zendesk integration guide.

Terraform Support for Event Orchestration Now Live
Create, maintain, and update event orchestrations at scale using Terraform. Check out the developer docs.

Service Standards GA starts ramping on June 20th
Use Service Standards to improve operational maturity and provide a better customer experience by establishing criteria that standardizes what ‘good’ looks like across teams. Configure services according to best practices and scale service ownership across the entire organization. This feature will begin ramping to customers on June 20th and should reach all customers by mid July. Learn more about Service Standards here.

Reauthorize Microsoft Teams Application
With PagerDuty’s authorization upgrade to Curity, our integrations will begin automatically refreshing expired tokens on a bi-yearly basis. Before PagerDuty can begin auto-refreshing the tokens for our Microsoft Teams’ customers, some customers’ teams will need to be initially manually refreshed. You will receive an email about this if you are currently using PagerDuty’s Microsoft Teams application for incident management and need to reauthorize your teams with old tokens.

Action Needed: Perform reauthorization for PagerDuty application in Teams with expired tokens as soon as possible:

  1. an instructional notification will be sent to the ‘general’ channel of all Teams with an old authorization token and
  2. the Teams user that originally completed the app authorization will receive a direct message prompting them to reauthorize.

Teams with old/expired tokens will no longer post incident notification into channels. Please reauthorize immediately to resume incident management in Microsoft Teams.

The notifications will walk you through Option 1 in Reauthorization Instructions.

Please Note:

  • You will only need to perform this action once; moving forward tokens will automatically be refreshed
  • Not all teams need to be reauthorized; if a team has an active token you will not be prompted and the application will refresh the token automatically. This update only impacts old expired tokens.

Action Owner: PagerDuty Admins, Account Owners, and Managers have the appropriate permissions to reauthorize Microsoft team connections to PagerDuty.

If you have any questions or concerns; please reach out to PagerDuty support for assistance.

May 2022

The refreshed Schedules List UI is now live
The Schedules List UI refresh is now generally available on all accounts. This new visual experience helps you find the information you need easier and faster while giving you more flexibility. Additionally, this page now allows for:

  • Enhanced search functionality
  • Toggling between all schedules and team schedules
  • Collapsing or expanding information based on the level of detail needed
  • Easier schedule comparison with time windows displayed
  • Streamlined view of on-call responders with shift times

Now ramping: Status update notification templates
Status update notification templates allow you to add the content and context you need for internal communications during incident response. Add logos and hosted third party images as well as format the text to company communication standards. Easily include incident details with a drop down menu that populates key information as needed. This feature has started ramping to customers and should reach all customers by mid June.

New SMS Formatting Standard for Incident Notifications
Starting May 23, PagerDuty will begin standardizing the way that incident notifications are formatted for SMS. Going forward, all SMS incident notifications (including status updates) will start with the prefix [PagerDuty]. Read the Knowledge Base article for more information.

New version of PagerDuty App for Splunk
The latest release of the PagerDuty App for Splunk (v 4.0.1) is now GA.

Maximum Open Incidents Per Service Set to 100K
There is a new product maximum of 100,000 open incidents allowed per service. With this change, services with over 100K open incidents will automatically have the auto-resolve setting enabled and set to 24 hours. This means that any new incidents on those services will be automatically resolved after they have been open for 24 hours and no further notifications will be sent for those incidents.

Most customers will see no impact. If you do run into this, it’s important to note that too many open incidents on a service is an indicator that your PagerDuty configuration could be optimized. To reduce the open incident count, we recommend using the update an incident API to bulk resolve incidents. Additionally, you can use this script for an automated way to bulk resolve incidents.

Update to Manage Incidents API
We’ve added two new product limits to the manage incidents endpoint to provide a better customer experience:

  • Maximum number of requests per minute to the endpoint will be limited to 500.
  • Maximum number of incidents that can be updated per API request will be set to 250 (previous limit was 500).
    We recommend that impacted customers update their scripts to disperse incidents updates out across a longer period of time. Please refer to our API documentation for more information.

Copy/Paste Event Orchestration Rules Now Available!
Users can now “copy” any Service Orchestration rule and then “paste” that rule into any Service Orchestration! With this feature, users can reuse rule conditions & actions, while still having the ability to tweak those conditions/actions for each specific service/orchestration. See the knowledge base article for [more information]. (

Event Orchestration + PagerDuty Automation Actions Integration
The integration between Event Orchestration and PagerDuty Automation Actions is live. By combining nested event orchestration with machine learning and precise, targeted automation triggers means that it’s possible to action an incident before responders even get paged. This integration helps teams automate common diagnostics and enable self-healing for recurring and well-understood types of incidents, resulting in reduced MTTR and escalations to specialists. To learn more, visit the PagerDuty Knowledge Base

April 2022

Safelist PagerDuty’s Webhooks IP Addresses
Starting on May 5, 2022, the official list of IP addresses that PagerDuty uses to send Webhooks calls will be provided on this page. Please safelist these IP addresses to ensure service continuity.

New AWS Plugins for Automated Diagnostics
By providing first-responders with diagnostic data that is typically only retrievable by domain-experts, the need to pull in more people for troubleshooting incidents is reduced significantly. New AWS plugins make it easier to get up and running with auto-diagnostics fast! Plugins with CloudWatch Logs retrieve diagnostic data from AWS infrastructure and applications. Systems Manager plugin allows users to manage their global VM footprint with security best-practices. Request a demo to learn more.

Customer Service Operations Integrations April Release (Salesforce Service Cloud v 3.5 and 3.5.1)

All release notes for 3.5 and 3.5.1 apply to the PagerDuty for Salesforce Service Cloud application located in the Salesforce AppExchange.

  • Integration with the new Salesforce Incident Management object. Bidirectionally integrate PagerDuty incidents with Service Cloud incidents, keeping both in sync and up to date. This feature also allows agents to manually link a PagerDuty incident to a Salesforce incident.
  • Ability to escalate PagerDuty incidents from the Salesforce command console.
  • Ability to add subscribers from the PagerDuty command console.
  • Ability to search for open incidents from the PagerDuty command console. This allows agents to quickly and easily link a Salesforce case to an existing PagerDuty Incident.
  • Enhanced PagerDuty Ruleset actions:
    • Ability to add a Salesforce user as an available dropdown option.
    • Ability to add subscribers in order to receive incident status updates.
    • Ability to automatically create a Salesforce incident after a PagerDuty incident is opened.
  • EU service region (v 3.5.1):
    • PagerDuty service regions allow customers to choose the geographic region of the PagerDuty data centers that host their account. Currently, the available options are the United States (US) and Europe (EU). For configuration details, please read the Salesforce Service Desk Integration Guide.
  • Performance Improvements:
    • Ability to enable or disable case creation or case comment triggers. If disabled, this will reduce the number of triggers. This also allows greater flexibility for companies that want to perform custom actions before the rule engine is invoked. This feature is found in Salesforce under PagerDuty Configuration Object Mappings tab.
  • Logging Improvements:
    • Improvements to reduce the number of logs created by the PagerDuty integration.
    • Log deletion queries now run once per day to delete logs more than 60 days old. This will help improve and mitigate past CPU and Disk usage issues.

Security Hygiene for the Current Cyber Threat Landscape
Given the current landscape, PagerDuty is preparing for increased instances of fraud and cyberattacks. Please take the necessary actions to protect your organization and users. Read about best practices to further secure your use of PagerDuty here.

Action required by Account Owners– Email Domain Restriction verification
PagerDuty is changing the default setting for the “Email Domain Restriction” feature in the Account Settings, to be ON by default (the current setting is OFF) for those accounts where it has not been enabled. For existing customers, this will be automatically enabled by April 15, 2022. With this update, the email domains will be restricted only to domains that are owned by the account. Note that this applies only to login email addresses, and not contact method email addresses.

The following exceptions apply to the automatic enablement of the Email Domain Restriction feature for existing customers:

  • Email addresses using common carrier domains (yahoo, gmail, aol etc.) will not be restricted.
  • The restriction will not be enabled for accounts with more than 10 email domains.

Take Action: Account owners should please check that the settings, and email domains and subdomains are set appropriately for your needs. For further details on this topic, please refer to this documentation page

Action Required – Migration from V1 & V2 webhook extensions to V3 webhook subscriptions
If you are currently using V1/V2 webhook extensions in your PagerDuty environment you need to migrate them to V3 webhook subscriptions to maintain functionality. Please follow our migration guide.

Who needs to take action? PagerDuty Admins, Account Owners and Team Managers.

Important Dates: V1 webhook extensions became unsupported (no new features or bug fixes) on November 13, 2021 and will stop working in October, 2022. V2 webhooks extensions will become unsupported in October, 2022 and will stop working in March, 2023.

Required Permissions:

  • Admins or Account Owners can migrate an entire account.
  • Team Managers can only migrate webhooks for their assigned Teams.

Improvements to the Business Service page
Find the business services you're looking for faster with improvements to the business service page. Now you can search for business services and navigate between pages to view the services you and your customers care most about.

March 2022

PagerDuty® Process Automation
We're excited to announce the latest offerings from our automation product line. We are officially rebranding our automation product line, Rundeck®, as PagerDuty Process Automation. Additionally, our runbook automation cloud service (announced last fall as “Rundeck Cloud”) is now generally available as PagerDuty Runbook Automation. Finally, we are announcing version 4.0 of Rundeck Enterprise, which will now be known as PagerDuty Process Automation On-Prem.

The PagerDuty® Process Automation portfolio consists of the following offerings:

  • PagerDuty® Automation Actions. A PagerDuty add-on that curates and connects responders in PagerDuty to automated diagnostics and remediation for services involved in incidents.

  • PagerDuty® Runbook Automation. A SaaS service that enables engineers to standardize and automate runbook procedures, and delegate services as self-service operations.

  • PagerDuty® Process Automation On-Prem. A self-hosted software cluster that gives engineers the ability to standardize and automate end-to-end operational workflows, and safely delegate them as self-service operations to stakeholders.

Watch our launch webinar where we dive into each feature.

Introducing status update notification templates!
Status update notification templates are now early access. This feature allows you to add the content and context you need for internal communications during incident response. As part of these new flexible templates, you can also add logos to your communications as well as format the text to company standards. If you are interested in being part of this early access program, fill out this form.

February 2022

Schedules List Page Improvements
The Schedules List page will be getting a UI refresh. This new visual experience helps you find the information you need easier and faster while giving you more flexibility. Additionally, this page now allows for:

  • Easier searching
  • Toggling between all schedules and team schedules
  • Filtering by variables like team, user, service, and more
  • Collapsing or expanding information based on the level of detail needed with compact and expanded view
  • Displaying time windows for all schedules on the page instead of advancing each schedule individually for easier schedule comparison
  • Streamlined viewing of who is on call and what their shift length is

Early access rollout to accounts will begin February 21, 2022. To see the new Schedules List page in action, watch this short demo.

January 2022

New Mobile Incident Details GA
The new mobile Incident Details screen provides you with a more compelling visual experience and easier access to all your favorite features during incident response. Run a play, add a priority or note, post a status update, and more with the new carousel. This improvement will be available to all customers by January 31, 2022. See what this looks like in action here.

Event Orchestration now available: Reduce noise and automate more using nested rules
Say hello to the next generation of event rules. Cut down on manual event processing. With Event Orchestration, you can create custom logic with nested rules to enrich, modify, and control routing or trigger automation actions based on event conditions at scale. Watch the demo here, read the knowledge base article, or sign up for the webinar to learn more about the feature on February 15. (This feature is only available to Event Intelligence; Enterprise for Incident Management and Digital Operations (Legacy) plans)

Round Robin Scheduling is now generally available
Round Robin allows teams to equitably distribute on-call shift responsibilities amongst team members. Automatically assigning new incidents across different users ensures that teams are resolving incidents as efficiently as possible with less risk of burnout. Round Robin is generally available for Business, Enterprise for Incident Management and Digital Operations (Legacy) plans.