ui/src/workflows/workflow-runs.ts:29-34 loadRuns calls api.tasks() with no query parameters and filters client-side. In internal/webui/api_tasks.go:94 GET /api/tasks defaults to limit=100. On busy instances where other tasks have run, a workflow's runs past the first 100 are invisible in the UI ('No runs yet', 0 running). Done when workflow runs use a workflow-filtered query or paging.
Imported from beads archie-core-tpiw1 · GitHub #1615 · type bug · priority P2 · created 2026-10-11 · closed 2026-10-11
ui/src/workflows/workflow-runs.ts:29-34 loadRuns calls api.tasks() with no query parameters and filters client-side. In internal/webui/api_tasks.go:94 GET /api/tasks defaults to limit=100. On busy instances where other tasks have run, a workflow's runs past the first 100 are invisible in the UI ('No runs yet', 0 running). Done when workflow runs use a workflow-filtered query or paging.
### Close reason
Fixed on fix/workflow-eda-audit (PR #1627)
---
_Imported from beads `archie-core-tpiw1` · GitHub #1615 · type bug · priority P2 · created 2026-10-11 · closed 2026-10-11_
sam
added the mediumbug labels 2026-10-27 13:41:01 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
ui/src/workflows/workflow-runs.ts:29-34 loadRuns calls api.tasks() with no query parameters and filters client-side. In internal/webui/api_tasks.go:94 GET /api/tasks defaults to limit=100. On busy instances where other tasks have run, a workflow's runs past the first 100 are invisible in the UI ('No runs yet', 0 running). Done when workflow runs use a workflow-filtered query or paging.
Close reason
Fixed on fix/workflow-eda-audit (PR #1627)
Imported from beads
archie-core-tpiw1· GitHub #1615 · type bug · priority P2 · created 2026-10-11 · closed 2026-10-11