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

# Browse failure patterns

> Open Failure patterns, discover from reports, and read why-it-matters plus next-state cues.

# Browse failure patterns

Open **Insights** / `/insights`. The mounted page title is **Failure patterns**.

<img src="https://mintcdn.com/evalgate/KV6BlM8ie_FdJpja/help/images/failure-patterns-list.png?fit=max&auto=format&n=KV6BlM8ie_FdJpja&q=85&s=43b2a100c7b0b695ad99e0bb1341297d" alt="A screenshot of Failure patterns with why-it-matters rows and Coverage missing next-state cues." width="1440" height="900" data-path="help/images/failure-patterns-list.png" />

## What to do

1. Click **Discover from failure reports** when you need new clusters from open
   reports (bounded lookback).
2. Read each row’s why-it-matters line and next-state cue (for example
   **Coverage missing**). Do not treat empty report counts as proof of absence.
3. Open a pattern to inspect membership, related evidence, and corrective
   actions.
4. Promote only after an approved review when the product requires it.

API and OpenAPI still use the `failure-topics` resource family. That name is not
the operator-facing title.

## Up next

[Inspect a trace](../traces/inspect-trace) that links to a pattern, or open
[Risks & controls](/docs/platform/risks-and-controls) when the failure is a control
gap.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.