#026Tutorial3 min

Find your previous analyses

Return to a saved report or use a project’s Scan history to select an older run.

Hackaiz team · updated 21/11/2026

Illustration: a person sets up an account on a laptop.
Illustration: a person sets up an account on a laptop. Illustrative photo, not a screenshot.

01Decide whether you need the latest report or an older run

A project and an analysis are not the same record. A project identifies the target; each analysis records a particular run. If you checked the same repository before and after a change, opening the project’s available report is not enough to establish which run you are reading. Use the analysis date and version to anchor your investigation.

For a recent result, start with Monitored projects. Search platforms lets you narrow the list by name, repository or address. Select a matching card to open its available report. If the project has no report, that card leads toward analysis instead. Do not start another run merely because you expected a history list at this point.

02Reach the project’s Scan history

The workspace magnifying glass provides a separate route into project details. Open Search and choose the project under Projects, rather than choosing the Monitored projects screen under Screens. On a computer, Ctrl+K or Command+K also opens this search. On a phone, tap the magnifying glass.

This shortcut lists only a limited selection, up to thirty projects. If the project you need is not offered, a saved project-detail address is useful. A saved report address takes you back to that particular analysis instead. Neither address is a public sharing permission: the workspace still uses your signed-in access.

  1. 1Open the workspace Search control.
  2. 2Find the project name in the Projects group and select it.
  3. 3Scroll to Scan history on the project detail page.
  4. 4Read each entry’s status, version and date before selecting the analysis you need.

03Use dates, versions and status together

Each history entry links to an individual analysis. The row includes its status, project version, start date and time, and number of findings. Where an older neighboring analysis exists, the history can also show the difference in finding count. These details help distinguish two runs made close together without relying on a project name alone.

A lower count is a useful clue, not proof that every earlier issue was fixed. The scope or completion state may differ between runs. Open the relevant reports and examine what was actually checked before treating the count difference as progress. A failed or interrupted run should not be presented as a clean security result.

For example, to document a release review, locate the analysis from before deployment by its date and version, then open the later run separately. Record both references in your own release notes. This preserves the distinction between the evidence you had at the time and findings that appeared after another change.

04Troubleshoot a report you cannot find

First remove the project-list search text and confirm the repository or address, especially if test and production share a similar name. If you kept the report address, reopen it while signed in. If you kept only a screenshot, use its visible date or version to select the matching history entry rather than guessing from the current finding total.

Pilot history is not the same screen as Scan history. The navigation label Pilot history refers to the assistant’s history; previous project analyses are listed on the project detail. This distinction matters when you remember a conversation about an issue but need the underlying analysis for a technical decision.

If the expected entry is still unavailable, contact Help with the project reference, approximate analysis date and the problem you see. Do not include passwords or database credentials. Browsing existing evidence should be your first recovery step; launching another analysis uses credits and creates new evidence rather than restoring the earlier run.

Frequently asked questions

Was this article helpful?

Related articles