The workflow list's run counts stop at the API's 200-run page #2114

Closed
opened 2026-11-22 00:20:21 +00:00 by sam · 1 comment
Owner

Why: GET /api/runs returns at most 200 runs, and the workflow list counts each workflow's runs from that page, so counts and last-run times are wrong once more runs exist.

Done when: the list reads per-workflow run counts and last run from the server (a summary operation or a filter by workflow) instead of counting a page client-side.

**Why**: GET /api/runs returns at most 200 runs, and the workflow list counts each workflow's runs from that page, so counts and last-run times are wrong once more runs exist. **Done when**: the list reads per-workflow run counts and last run from the server (a summary operation or a filter by workflow) instead of counting a page client-side.
sam added the buglow labels 2026-11-22 00:20:21 +00:00
Author
Owner

Landed in de3bfe296: GET /api/workflow-stats returns each workflow's run count, last run and success rate from the server, and the workflow list reads it instead of counting the 200-run page. task check passed; deployed to staging.

Landed in de3bfe296: GET /api/workflow-stats returns each workflow's run count, last run and success rate from the server, and the workflow list reads it instead of counting the 200-run page. task check passed; deployed to staging.
sam closed this issue 2026-11-22 04:12:36 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#2114