Skip to content

Issues

The Issues view shows conversations that have been flagged for human review. Issues help you catch problems and ensure quality.

Creating an Issue

Issues are created manually by team members reviewing conversations. The quickest way is to click the Create Issue (bug) button directly on an event card in the Conversation detail view — it pre-fills the conversation ID, event index, and stage automatically.

You can also create issues from scratch using the Create Issue button on the Issues list page.

Issue Form

When creating or editing an issue, the form contains:

FieldRequiredDescription
ProjectYesThe project this issue belongs to. Auto-filled when opened from a conversation.
StageNoThe stage where the problem occurred. Auto-filled when opened from an event card.
Conversation IDNoThe conversation where the issue was observed. Auto-filled when opened from a conversation. If set on an existing issue, a link icon lets you navigate directly to that conversation.
EnvironmentNoThe environment where the issue was found.
Build VersionYesThe build or release version when the issue was observed (e.g., v1.2.3).
CategoryYesThe type of issue: intent, ai answer, entity, or tool.
SeverityYesImpact level: critical, major, minor, or trivial.
StatusYesCurrent state of the issue (see below). Only editable when updating an existing issue.
Bug DescriptionYesA clear description of what went wrong.
Expected BehaviourYesWhat the AI should have done instead.
CommentsNoAdditional notes or context.

Issue Statuses

StatusMeaning
awaitingNewly created, not yet investigated
in-progressSomeone is actively working on it
ready-to-testA fix has been applied and is ready for verification
still-occursTested but the problem persists
doneResolved and verified
cannot-reproduceCould not be reproduced
wont-fixAcknowledged but not going to be fixed

Working with Issues

Use the Issues view to:

  • Triage incoming issues — review what went wrong and decide if action is needed.
  • Investigate — Click through to the linked conversation to see the full event log and trace the problem.
  • Resolve — Update the status as work progresses through to done.

Tips

  • Check issues regularly — They're your early warning system for problems in conversation design.
  • Look for patterns — If the same kind of issue keeps appearing, it usually means a stage prompt, classifier, or action needs improvement.
  • Use with audit logs — If an issue started after a recent change, check the audit logs to see what was modified.

Released under the Apache-2.0 License.