# Work through an agent's issues

Read the Profiler's Issues tab, where bad answers, exceptions and SLO breaches are grouped by what is broken, with sample traces and the action for each kind.

**Issues** is everything wrong with the agent, grouped by what is actually broken rather than by what threw. A bad answer is an issue here, not only an exception.

**Who can use it:** the **Builder** role or higher, in a tenant licensed for agents.

## The headline figures

![The Profiler Issues page: five figures for helpful rate, refusal rate, hallucinated, exception rate and open groups, filter chips for All, Quality, Exceptions, SLO breaches and Guardrail blocks, a list of groups each with a kind badge and an occurrence count, and beside it the selected group with its sample traces, each giving the question, the judge score and the latency, above Open Optimizer.](https://docs.katonic.ai/img/agents/profiler-issues/profiler-issues.png)
*Issues groups everything wrong with the agent by what is broken: bad answers, exceptions and SLO breaches, with the headline rates above them.*

Five figures open the page: the **helpful rate**, counting judge scores of four and above; the **refusal rate**, where the agent declined to answer; **hallucinated**, as flagged by the judge; the **exception rate**, as a count of traces whose spans ended in error; and the number of open groups, broken down by kind. A figure the platform has not measured reads as a dash, never as zero.

The filter chips are **All**, **Quality**, **Exceptions** and **SLO breaches**, each with its count, beside a refresh control and an export that downloads the groups and figures as JSON.

## The groups

Each group carries a badge naming its kind and, for a quality group, what kind of quality problem it is: refused, hallucination or low judge score. Under the title sit the message or a snippet, the node the group is attributed to where the platform knows it, and how many times it occurred in the window.

Selecting a group fills the rail on the right, and what you get there depends on the kind.

| Kind | The rail shows | Its action |
| --- | --- | --- |
| **Quality** | The message and sample traces with their questions, scores and latencies | **Open Optimizer** |
| **Exception** | The captured exception in a code block, and sample traces | **Open in Developer Hub** |
| **SLO breach** | How many traces breached which threshold, and sample traces | **Investigate node**, enabled only when the group is attributed to one node |

A sample trace opens [that trace in full](/agents/profiler-trace-detail). Each rail also offers a share control.

## When there is nothing

**No issues detected** is the healthy state, and the note under it says when each kind of group can appear at all: quality clusters once the judge has evaluated enough traces, exception groups when spans complete with an error status, and SLO groups when a configured SLO is breached. A healthy agent stays empty, which is the point.

## Troubleshooting

- **Couldn't load issues.** The observability service returned an error. The message says this is a service error, not a healthy agent, and **Retry** repeats the request.
- **No quality groups, ever.** The judge runner is not evaluating this tenant's traces. The empty state names that as the first condition.
- **Investigate node is dimmed.** The breach group is not attributed to a single node, and the tooltip says so.

## Related

- [Profiler](/agents/profiler)
- [Read one trace in full](/agents/profiler-trace-detail)
- [Look at one node](/agents/profiler-node)
- Platform alerts

Source: https://docs.katonic.ai/agents/profiler-issues
