---
title: "Find a particular change among an investigation’s leads | Proofline Help"
description: "On an investigation’s Summary tab, open the full candidate list to find a change outside the first few results. You can narrow the list to deployments or reviewed commits."
url: https://proofline.sh/help/investigation-ranked-changes/
---

[Help center](/help/)

# Find a particular change among an investigation’s leads

On an investigation’s Summary tab, open the full candidate list to find a change outside the first few results. You can narrow the list to deployments or reviewed commits.

## Search Where to look

**Where to look** lists candidate changes, most likely first. The ranking covers every change in the window, often hundreds, so it names the first few and the link below them counts and opens the rest. A merge that was in the latest deploy before the symptom ranks above one that was not deployed by then. A configuration change names the fields Kian saw change, or says that the resource was added or removed. When Kian recorded the resource changing the same way more than once in the window, the time beside it adds how many changes Kian recorded and over how long, such as **one of 62 changes over 20h**, and Slack, PagerDuty and pull request replies add the same words. A resource that something rewrites all day always has a change shortly before the symptom, so its latest change is weak evidence on its own. A Cloud Run revision that was added and later removed shows no count. Select **Recorded changes** under it to list each change Kian found to the resource: what changed, and that it changed after the earlier collection and no later than the later one, with where that interval falls against the symptom start. When two of Kian's inventory reads found the same change, it is listed once, over the time both allow, and **Kian references** under it names the collections each read compared. Proofline records neither the values nor who made the change. A Cloud Run revision that was added or changed shows **Runs** and the commit from the revision's `commit-sha` label. When a merge or deploy in this investigation's timeline has the same commit, the line names its pull request or commit title and its repository, links them, and cites that timeline entry. Otherwise the commit appears as the label records it, with a copy button and no link, because the label alone does not say which repository the commit belongs to. A revision without the label shows no commit. Use **View deploy**, **Deploy history** or **View review** when available to inspect a candidate's deployment or review. A candidate that Proofline left out of code review shows **View exclusion** instead of **View review**: the repository's review scope left its pull request out, sampling did not choose it, or it only promoted commits already on another protected branch. The exclusion records that Proofline read none of the change's code. Ranked leads are starting points for investigation; they do not establish a cause.

After you open the rest, search the changes by title, repository or commit, or use **Show** to list only **Deployed here** or **With a review**.

## Related guides

-   [Find an environment's investigations](/help/environment-investigations/)
-   [Create an environment](/help/create-environment/)
