Changelog

September 3, 2026

Related Incidents detected automatically.

Related Incidents detected automatically.

Rootly's agent now posts the most closely related past incidents directly into the incident channel in Slack. Nobody has to ask for it. Each match arrives with the reason it is relevant, how severe it was, how long it took to resolve, and a link back to the original incident.

Rootly keeps looking on your behalf. As an incident opens, the agent searches your incident history in the background and, when it finds one that is genuinely relevant, shares it with the response team on its own. Nobody has to stop and run the search, and nobody has to already know what to search for.

You get at most three matches in a compact message that threads the details, so the incident channel stays readable, and the card can be dismissed when it isn't useful.

Rootly's Slack Agent will post up to 3 related incidents in your Incident channel, helping you respond more quickly by learning from past incidents.

What's included

  • Related past incidents posted automatically into the incident's Slack channel, with no prompt needed.
  • Up to three matches per message, each showing why it was matched — the same service, a similar kind of failure — along with severity and time to resolve.
  • Links back to the full incident, so anyone can read the original response without leaving Slack.
  • A compact message that threads the details, keeping the incident channel clear.

Why it matters

Most teams have already responded to a version of the incident in front of them. That knowledge sits with whoever happened to be on that response, and in write-ups nobody thinks to search at 3 AM. The person holding the pager tonight is usually not the person who solved it last time.

Putting the match in the channel closes that gap. Responders start from what the last team learned — what it was, how bad it got, how long it took, how it was fixed — instead of spending the first stretch of the incident searching for it. Less time on research, more time on the fix, and a shorter path to mitigation.

“Rootly's proactive related incidents detection replaced hunting through old postmortems to figure out the last time an incident happened, saving us time and keeping our attention on the fire at hand!”
— Mark Shaw, Faire Engineering

Start learning from Related Incidents now by turning the feature on in your AI & Agents settings. Learn more in our Help Docs.

What else shipped

Improvements

On-Call

  • Assign a schedule to a Slack User Group across many Slack Workspaces.

Incident Response

  • Sync a ServiceNow CMDB into your Rootly catalogs.
API

On-Call

  • Outbound alert webhooks now carry more of the alert's details.
  • An escalation path read through the API can now be sent straight back with PUT.
  • Listing on-calls filtered by user is much faster and no longer times out.

Incident Response

  • Request bodies across the API now use one consistent shape, so generated clients pick the right variant.
Terraform
  • The rootly_services data source now pages through every service instead of silently stopping at the first 50.
MCP Server
  • Shift date ranges are now split into chunks the API accepts, and out-of-range requests are caught before they are sent.
  • Result count settings are now adjusted to the supported range instead of being rejected.
  • Shift date ranges are now named start_date and end_date, with the old from and to names still accepted.
  • More argument name aliases are accepted, including limit.
Fixes

On-Call

  • The escalation policy Slack channel picker now lists channels for people whose Slack account lives in a secondary workspace.
  • New users added through single sign-on now get your organization's timezone instead of Pacific.

Incident Response

  • Creating a task from a Slack form now confirms that it worked.
  • Incident links posted in Slack show a preview.

You and your teams deserve
modern incident management.

Get a 1:1 demo with one of our technical staff or start your free 14-day trial.