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

# Issues

> Find and fix your agent's most common failures.

With Issues, Bluejay identifies common problems with your agent from production calls.

If you are tracking issues from simulation results, see [Issues](/test/issues.md).

![The production Issues list with one row for each issue, showing its priority, status, failure mode, conversation count, and percent of conversations](https://mintcdn.com/bluejay/EeUk0hD_moG9tWmI/images/issues-list-monitor.png?fit=max\&auto=format\&n=EeUk0hD_moG9tWmI\&q=85\&s=8f997e8cea49239d839f72e4985f787d)

## How issues work

After Bluejay evaluates a production conversation, it finds where the call went wrong and matches each failure to similar failures from your other conversations.

Each issue has a failure mode:

* **Agent Failure**: the agent had a failure based on its conversations (transcripts).
* **System Error**: a tool call failed, the voice platform reported an error, or the agent got stuck repeating the same tool call.

## Work through an issue

**1. Open the top issue**

Start with the issue that hits the most conversations, and read a few of its conversations to see what the agent did.

**2. Find the cause**

Click **Investigate** to ask [Bluejay AI](/improve/bluejay-ai.md) what to change, or **Fix** to copy a prompt for your coding assistant.

**3. Track the work**

After your fix ships, monitor the failure with an [alert](/monitor/alerts.md) on a [custom metric](/monitor/metrics.md) that checks for it.

## Related

* [Issues API](/api-reference/endpoint/list-issues.md)
* [Alerts](/monitor/alerts.md)
* [Logs](/monitor/logs.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.