> ## The triage report

> The triage report in Antithesis

> Fetch the complete documentation index at: https://antithesis.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

---

The **triage report** provides a high-level overview of your most recent test run, and a longer history of **[Findings](/docs/product/reports/findings/)**. Every time you [launch a test](/docs/product/test_launchers/), Antithesis generates a triage report and emails it to your team.

The pages below offer a detailed explanation of the triage report. We also have a **[list of common workflows](/docs/product/reports/findings/#common-workflows)** to help you jump right in.

The main sections of the triage report are:

1. **[Findings](/docs/product/reports/findings/)** summarize calls to action based on your test (for most users, this is the most important piece).
2. **[Environment](/docs/product/reports/environment/)**, a description of the software that was tested.
3. **[Utilization](/docs/product/reports/utilization/)**, high-level statistics about the run as a whole.
4. **[Properties](/docs/product/reports/properties/)**, individual pass/fail information about each of your test properties.

For a given failure that you see in the **Properties** section, you can generate a [causality analysis report](/docs/product/debugging/causality_analysis/), which gives you more information about the timing of events that trigger that bug.

The pages above are based on our [interactive example triage report](/reports/example-triage-report), which was generated from an actual Antithesis test run. We encourage you to open it in another tab and follow along.