The workflows sidebar derives each workflow's running count and last status from the newest 100 tasks across all workflows, so a quiet workflow shows nothing. Use the per-workflow task filter (GET /api/tasks?workflow=) or a summary query. Done when a workflow whose runs are all older than the newest 100 tasks shows its real status.
Close reason
The workflows sidebar no longer derives a workflow's state from the newest 100 global tasks. WorkflowStats now carries running (COUNT FILTER status='running') and last_status (newest row's status by id) in the SQL, the state contract, storecontract and staterpc mapping, so GET /api/workflows answers per workflow; WorkflowsPage drops the global api.tasks call and reads row.running/row.last_status. Verified the query and its semantics against the dev PostgreSQL 18: a quiet workflow with an old merged run plus a newer running one reports running=1/last_status=running while a stale one reports its newest status, and test-source rows stay excluded.
Imported from beads archie-core-5e2ai · GitHub #1630 · type bug · priority P2 · created 2026-10-11 · closed 2026-10-26
The workflows sidebar derives each workflow's running count and last status from the newest 100 tasks across all workflows, so a quiet workflow shows nothing. Use the per-workflow task filter (GET /api/tasks?workflow=) or a summary query. Done when a workflow whose runs are all older than the newest 100 tasks shows its real status.
### Close reason
The workflows sidebar no longer derives a workflow's state from the newest 100 global tasks. WorkflowStats now carries running (COUNT FILTER status='running') and last_status (newest row's status by id) in the SQL, the state contract, storecontract and staterpc mapping, so GET /api/workflows answers per workflow; WorkflowsPage drops the global api.tasks call and reads row.running/row.last_status. Verified the query and its semantics against the dev PostgreSQL 18: a quiet workflow with an old merged run plus a newer running one reports running=1/last_status=running while a stale one reports its newest status, and test-source rows stay excluded.
---
_Imported from beads `archie-core-5e2ai` · GitHub #1630 · type bug · priority P2 · created 2026-10-11 · closed 2026-10-26_
sam
added the mediumbug labels 2026-10-27 13:38:57 +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.
The workflows sidebar derives each workflow's running count and last status from the newest 100 tasks across all workflows, so a quiet workflow shows nothing. Use the per-workflow task filter (GET /api/tasks?workflow=) or a summary query. Done when a workflow whose runs are all older than the newest 100 tasks shows its real status.
Close reason
The workflows sidebar no longer derives a workflow's state from the newest 100 global tasks. WorkflowStats now carries running (COUNT FILTER status='running') and last_status (newest row's status by id) in the SQL, the state contract, storecontract and staterpc mapping, so GET /api/workflows answers per workflow; WorkflowsPage drops the global api.tasks call and reads row.running/row.last_status. Verified the query and its semantics against the dev PostgreSQL 18: a quiet workflow with an old merged run plus a newer running one reports running=1/last_status=running while a stale one reports its newest status, and test-source rows stay excluded.
Imported from beads
archie-core-5e2ai· GitHub #1630 · type bug · priority P2 · created 2026-10-11 · closed 2026-10-26