> For the complete documentation index, see [llms.txt](https://docs.duku.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duku.ai/core-concepts/issues-and-signals.md).

# Issues & signals

How Duku turns the errors it finds into a short list of distinct problems.

Duku turns run errors into a concise list of distinct problems.

#### From errors to issues

A run produces errors. Errors with the same signature are collected into a **signal**. Signals with one underlying cause are collected into an **issue**.

This keeps a broken endpoint in one issue, not a dozen near-identical rows.

#### Issues and signals views

Where grouping is enabled, the dashboard offers two views:

* **Issues** shows one entry per problem.
* **Signals** shows each individual error on its own.

Use the [Issues](/viewport-dashboard/issues.md) to review either view.

#### Counts

An issue's **issue count** is the number of signals behind it. Its **occurrence count** is the number of distinct runs that hit it.

Occurrence count does not count every error seen during those runs.

#### Status and priority

Status and priority are set on the issue. They apply to everything grouped into it.

A status you set never changes back automatically.

Use the [Issues API](/integrations/issues-api.md) to read issues and signals, or write status and priority changes.