Skip to main content
This guide covers the day-to-day of an AI investigation on a live incident: reading findings, weighing in, getting a summary in chat, and approving an action.

​
Prerequisites

  • A plan that includes AI Investigations (Pro or Enterprise).
  • A critical incident (auto-run only fires at critical severity — you can also start a run by hand on any entitled incident).

​
Read and weigh in on findings

1

Open the Findings panel

On the incident page, the Findings panel lists each finding with its kind, a one-line summary, a confidence percentage, and links to its evidence.
2

Open the evidence

Follow a finding’s evidence link to the source — a past incident, a deploy, or a Sentry issue — to judge whether the diagnosis holds.
3

Confirm or dismiss

Click Confirm on a finding you agree with, or Dismiss on one that doesn’t apply. This records the team’s judgment; it does not change the incident’s status.
4

Run again if the picture changes

As the incident develops — a new deploy, a fresh Sentry error — click Re-run to start another pass over the current signals.
Seeing no findings is meaningful. scaling.cloud only posts a finding when its confidence clears an internal floor, so an empty panel means nothing matched with enough confidence — not that the investigation failed to run.

​
Get a summary in chat

In the incident’s Slack or Microsoft Teams channel, mention @scaling to get a live summary synthesized from the current findings, without leaving chat. The summary reflects the latest run, so mention it again after a re-run to refresh it.

​
Approve a proposed action

Some findings propose a next step — file a ticket, post to a channel, attach a runbook. These appear in the Proposed actions panel.
1

Review the proposed action

Each proposed action names what it will do (e.g. “Create a Linear issue”). Open it to see the details.
2

Approve or dismiss

Click Approve to run it, or Dismiss to clear it. Nothing runs until you approve — the AI never acts on its own.
3

Confirm the outcome

On approval, scaling.cloud executes the action and records the result on the incident — for a create-ticket action, the linked ticket appears on the incident.
A create ticket action needs your issue tracker connected. Connect Linear under Settings → Integrations first — see Proposed actions.

​
After resolution

When you resolve the incident, its post-mortem draft is pre-filled from the findings — root cause and contributing factors are seeded, so your retro starts from a draft instead of a blank page.