Skip to content

Surface parked waiting runs in health buckets - #76

Merged
mikeyobrien merged 1 commit into
mainfrom
cursor/waiting-health-bucket-b0f1
Aug 31, 2026
Merged

mikeyobrien merged 1 commit into
mainfrom
cursor/waiting-health-bucket-b0f1

Conversation

@mikeyobrien

Copy link
Copy Markdown
Owner

Parked durable waits use status=waiting and have no live PID. Run health only bucketed active / watching / stuck / failed / completed, so those runs disappeared from autoloop loops health and GET /api/runs.

Change

  • categorizeRecords classifies status=waiting into a waiting bucket (no PID required; not dropped by the 24h recent window).
  • autoloop loops health (text and --json) and GET /api/runs include that bucket.
  • Dashboard run-list docs list waiting alongside the other health sections.
  • Existing buckets stay the same.

Tests

  • A record with status=waiting and no PID is classified as waiting, not dropped.
  • Waiting runs appear in health JSON and GET /api/runs.
  • Active / watching / stuck / failed / completed classification is unchanged.

Memory stays on the default jsonl plugin. This does not add a wait card UI, extra dashboard chrome, or a parallel wait API.

Open in Web Open in Cursor 

categorizeRecords dropped status=waiting records, so parked durable
waits disappeared from loops health and GET /api/runs. Add a waiting
bucket and list it on those surfaces alongside the existing ones.

Co-authored-by: Mikey O'Brien <m@mobrienv.dev>
@mikeyobrien
mikeyobrien marked this pull request as ready for review August 31, 2026 16:56
@mikeyobrien
mikeyobrien merged commit 9ba5687 into main Aug 31, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants