Skip to content

Quality tab

Operational quality signals for the agent — whether runs are completing, how long they take, and where the failures are — computed from instances and spans started in the last 24 hours. Come here when you want to know if the agent is healthy before digging into individual runs.

For the fixed strip that stays visible above the tab row, see the Agent page. For quality evaluations of individual runs — scores and verdicts rather than run health — see the Agent › Instance › Quality tab.

Four headline figures for the last day: Success rate (the share of finished runs that completed successfully), Typical duration (the average finished instance), Worst case (the longest), and Failures (runs that finished as Failed or Terminated).

Below the headline figures, the instance duration distribution breaks finished runs down by Best, P25, Median, Average, P95, Worst, and standard deviation, so a healthy-looking average cannot hide a bad tail.

Every instance from the last 24 hours by how it ended — Complete, Failed, Cancelled, or Terminated — with counts and percentages.

The same timing analysis at span level, grouped by span type across schema versions and sorted by average duration. Each span type shows its call count, success rate, failure count, and duration spread (min, p25, median, p95, max, and average) on a shared time axis, so the slowest step in the agent’s workflow stands out. Only activity spans are counted here; quality spans written by the platform are excluded.