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

# Issues

> App bugs, UX suggestions, and unclear instructions flagged in your flow runs

**Issues** flag the cause of a test failure, a UI/UX improvement, or an unclear test instruction, and cite exactly where in the run or instructions it occurred.

Individual issues are grouped in the background into **Issue Groups**, shown on the [Issues](https://autosana.ai/issues) and [Overview](https://autosana.ai/overview) pages.

<iframe width="100%" height="400" src="https://www.youtube.com/embed/UkByv35DeC4?si=AW_o4whNPJO2PVD7" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen />

## Individual Issues

Issues are generated per flow run. View them on a flow run directly, or through the occurrences in an issue group. A flow run shows *what* happened; an issue group shows *where* similar issues happened across your runs.

Each issue has the following properties:

| Property                                                                    | Description                                                                                                                                                                                                               |
| --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Title**                                                                   | A concise identifier for the issue.                                                                                                                                                                                       |
| **Description**                                                             | A clear explanation of the issue.                                                                                                                                                                                         |
| **Severity** (`critical`, `major`, `minor`)                                 | The impact level of the issue. Critical issues cause a test to fail; major and minor issues are flagged but don't fail the test.                                                                                          |
| **Type** (`functional`, `ui`, `ux`, `performance`, `state`, `instructions`) | The testing facet the issue falls under. Instruction issues flag a problem in the test itself rather than your app, and show in blue instead of the usual red, orange, and yellow (critical instruction issues stay red). |
| **Instruction highlighting**                                                | The instruction line(s) the issue refers to.                                                                                                                                                                              |
| **Action references**                                                       | The action(s) where the issue occurred. These need not be consecutive.                                                                                                                                                    |

## Issue Groups

An **Issue Group** collects individual issues that describe the same underlying problem, even when they occur on different runs, flows, apps, or devices. Grouping is semantic, so issues match on meaning rather than exact wording, and runs in the background: new issues join existing groups automatically, duplicate groups merge, and overly broad groups split.

Each group falls into one of three categories:

* **Critical**: App bugs responsible for test failures. Any group that contains a critical issue.
* **UI/UX**: Visual, usability, and performance improvements that didn't fail the test.
* **Instruction**: Instructions the agent found ambiguous, contradictory, or impossible on the current build. These point to the test, not your app.

A group shows:

* **Occurrences**: The total times the problem has been seen.
* **Affected flows, apps, devices, and builds**: The places where it occurs.
* **Severity breakdown**: The count of critical, major, and minor issues in the group.
* **First and last seen**: The times when the problem started and when it last occurred.
* **Evidence**: The runs where it occurred, each with a screenshot from the exact action.

<Note>
  Use **Copy link** on any issue group to easily share it.
</Note>

### Triage

Every group has a status. Use the status toggle on the Issues page to filter by **New**, **Dismissed**, **Closed**, or **All**.

| Action               | Result                                                        |
| -------------------- | ------------------------------------------------------------- |
| **Mark as complete** | Dismisses the group. It returns if the problem happens again. |
| **Don't show again** | Closes the group. It stays hidden even if the problem recurs. |
| **Restore / Reopen** | Returns a dismissed or closed group to the board.             |

Statuses are shared across your workspace.

## Next Steps

* [Learn how flows are reviewed](/flows)
* [Get notified when runs complete](/notifications)
* [Track performance metrics on every run](/performance-monitoring)