Skip to content

bug(ui): Health tab shows no circuit-breaker state for agents whose breaker is DORMANT #3452

Closed

Description

@vybe

Summary

Rows read only "Critical … Container: exited"; GET /api/monitoring/status reports four dormant breakers with up to 825 recorded failures.

Category: functional · Severity: Medium · Validated: API

Context

Found by the click-through UI sweep of a local instance (dev @ c90c711ee, 1.0.0-rc1), fixture agents only.

Repro

  1. Have agents stopped long enough for their dispatch breaker to go dormant.
  2. Open /operations?tab=health.

Expected

Honest status: the breaker state the API reports is visible where fleet health is shown.

Observed

Rows read only "Critical … Container: exited"; GET /api/monitoring/status reports four dormant breakers with up to 825 recorded failures.

Validation

API response of GET /api/monitoring/status versus the rendered rows, in two runs.

Acceptance Criteria

  • The repro above gives the Expected result at 1440 and 768, in light and dark.
  • A regression test pins the behaviour (unit or Playwright, whichever tier can observe it).
  • No new raw-palette classes or hand-rolled primitives are introduced by the fix (docs/memory/design-system-contract.md).

Technical Notes

Evidence screenshots (kept on the machine that ran the sweep; the evidence folder is gitignored because the repository is public):

  • docs/testing/ui-sweep/evidence/2026-10-09-all/05a55425-1.png

Found by /ui-sweep --all @ c90c711

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions