Skip to main content
An investigation is scaling.cloud’s diagnostic layer for an incident. When a high-impact incident opens, scaling.cloud reads the signals it can reach — your past incidents, recent code changes, and connected error tracking — and posts findings: short, confidence-scored statements about what is likely going on, each backed by evidence you can open. Investigations never act on their own. Every finding is a suggestion you confirm or dismiss, and any action a finding proposes waits for a human to approve it. See Proposed actions.

​
The shape of an investigation

​
What gets investigated

Investigations run automatically only when both conditions hold:
  • Your organization is on a plan that includes AI Investigations (Pro or Enterprise — see Pricing).
  • The incident’s severity is critical.
The gate is severity, not how the incident was opened. A critical incident that an alert opened automatically at 3am is investigated just like one a person declared — exactly when no one is awake to start digging.
Incidents below critical, and all incidents on the Free plan, do not auto-run. You can still open the investigation panel on any entitled incident and start a run by hand.

​
Findings

Every finding carries: Findings are produced with an origin of ai — the same attribution model the rest of the timeline uses to distinguish machine actions from human ones (see Origin).
scaling.cloud stays quiet when it is unsure. A finding is only posted when its confidence clears an internal floor, so a cold-start incident with no matching signal produces silence, not noise.

​
Confirming and dismissing

In the incident’s Findings panel, each proposed finding has Confirm and Dismiss controls. Confirming records that a responder agreed with the diagnosis; dismissing clears it. Neither changes the incident’s status — findings inform the humans running the incident, they do not drive the lifecycle.

​
Where findings show up

Findings are surfaced where responders already work:
  • Incident page — the Findings panel lists every finding with its confidence and evidence, and lets you confirm, dismiss, or start another run.
  • Chat — tag @scaling in the incident channel for a live summary synthesized from the findings (Slack and Microsoft Teams). See Work with AI findings.
  • Post-mortems — when a post-mortem draft is created on resolution, its root-cause and contributing-factors sections are pre-filled from the findings, so your retro starts from a draft instead of a blank page.

​
Where findings come from

The first run of every investigation looks at your own resolved incidents. Once you connect a code or error-tracking source, later runs draw on those too:

Signal sources

Past incidents, GitHub changes, and Sentry errors — the inputs a run reads.

Proposed actions

How a finding can propose a next step for a human to approve.