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

# Issues

> Recurring problems grouped by root cause, ranked by impact

**Issues** is an inbox of recurring problems your agents hit, grouped by root cause and ranked by affected sessions. Work the top of the list, and archive what's fixed.

These are product failures, not just exceptions — an agent looping on a missing auth scope, search missing the word "refund", an export truncated by pagination. Armature finds them **even when every API response was 200 OK**.

## The inbox

Two tabs — **Open** and **Archived** — with counts. Each issue row shows:

| Column                  | Meaning                                                                                                                    |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Issue**               | Title, one-line summary, and a cause category pill (schema change, error message, tool description, performance, auth, …). |
| **# affected sessions** | The blast radius in the selected range, with a comparison bar.                                                             |
| **Last seen**           | When a session last hit this issue (or when it was archived).                                                              |

Filter by category, search by title or text, and sort stays impact-first: *ranked by affected sessions*.

## Issue detail

Opening an issue shows the root cause, its in-range blast radius — sessions, tools, use cases, and clients affected — and example sessions. Jump into a [session replay](/dashboard/sessions) to watch a real user hit the problem, then fix it at the source.

## Lifecycle

* **Detection** — when a session fails, models extract concrete problem statements ("`search_invoices` returns empty results when the query includes a date filter"). Statements that recur across sessions are clustered into one issue with a generated title, summary, and cause category.
* **Archive** — click **Archive** when an issue is fixed; **Restore** brings it back. Issues that stop recurring for three weeks archive automatically, so the open tab reflects what's happening *now*.