---
title: Issue Management
description: Workflows for triaging, investigating, and resolving issues
---

# Issue Management

Once Latitude discovers issues, your team needs workflows to triage, investigate, and resolve them. This page covers practical approaches to issue management.

## Triage Workflow

When new issues appear, your team should:

1. **Review the issue description**: Understand what failure pattern was discovered
2. **Examine example traces**: Click into specific traces to see the actual conversations where the issue occurred
3. **Assess severity**: Is this a critical safety issue, a quality degradation, or a minor edge case?
4. **Decide on action**:
   - **Generate an evaluation** to start automated monitoring
   - **Save a search** scoped to the issue's traces and assign it to a reviewer to gather more human feedback
   - **Ignore** if the issue is irrelevant or too rare to track

## Investigating an Issue

For issues that need deeper investigation:

### Review Example Traces

Each issue links to the traces where it was detected. Read through several examples to understand:

- What kinds of user inputs trigger the issue?
- Is the agent consistently wrong, or is it intermittent?
- Are there common patterns in the conversation context?

### Check Related Evaluations

If the issue has linked evaluations, review their configuration:

- Is the evaluation too strict? (Flagging acceptable behavior)
- Is it too lenient? (Missing obvious failures)
- Does the trigger configuration need adjustment?
- What does the alignment (MCC) look like?

### Gather Human Feedback

Run a search filtered to traces where the issue was detected and save it. Assign the saved search to a reviewer, who can work through the matches one by one in the trace detail view. Annotations on these traces:

- Confirm whether the automated detection is correct
- Provide richer feedback about what went wrong
- Build alignment data for the linked evaluation

## Resolving Issues

When your team has fixed the underlying problem:

1. Navigate to the issue detail page
2. Click **Resolve**
3. A confirmation modal appears with a **keep monitoring** toggle

The keep monitoring toggle determines what happens to linked evaluations after resolution:

- **Enabled**: Linked evaluations stay active so they can detect regressions. If the issue reappears, it moves to **Regressed** state.
- **Disabled**: Linked evaluations are archived when the issue resolves.

The toggle defaults from your project settings, falling back to the organization-level setting when the project doesn't have one set. You can override the default for each specific resolve action.

## Working with Regressed Issues

A regressed issue means a previously resolved problem has returned. This is a high-priority signal:

- The fix may have been incomplete
- A new code change may have reintroduced the problem
- The agent's behavior may have drifted due to model updates

When an issue regresses:

1. Review the new occurrence traces. Are they the same failure pattern or something subtly different?
2. Compare with the original resolution. What changed?
3. Fix and re-resolve

## Ignoring Issues

Ignoring an issue is separate from resolving it:

- Ignoring **immediately archives** all linked evaluations, regardless of the keep monitoring setting
- Ignored issues are hidden from default views but can be un-ignored later
- Use ignore for issues that aren't worth tracking, not for issues that have been fixed

## Organizing Issues

As your project matures, you'll accumulate many issues. Keep them manageable:

- **Resolve fixed issues** rather than leaving them open. Keep monitoring enabled catches regressions
- **Ignore irrelevant issues**: Don't let noise drown out real problems
- **Use issue descriptions** to communicate context: future team members will read them
- **Link related evaluations**: Every meaningful issue should have an evaluation monitoring for it

## Next Steps

- [Issues Overview](./overview): How issues are discovered
- [Evaluations](../evaluations/overview): Generating evaluations from issues
- [Saved Searches](../search/saved-searches): Build a review workflow around an issue's traces
- [Annotations](../annotations/overview): Leave human feedback on traces tied to an issue
