webui: /api/workflows serves no definitions from the archie-ui composition #1041

Closed
opened 2026-10-27 13:38:47 +00:00 by sam · 0 comments
Owner

Found while fixing archie-core-rcbf. GET /api/workflows on the dev stack
returns definitions: [] alongside workflows: [{workflow: "implement", runs: 1, ...}], while the daemon logs "workflow registry built workflows=7" at startup.

The registry lives in the daemon; the archie-ui process serving this endpoint
does not have it, so it answers with an empty definition list.

Two consequences in the UI:

  • The Per workflow empty state used to key off definitions alone, so the page
    claimed "No workflow runs yet" directly above the stage tables listing those
    runs. Fixed on the UI side in workflow-rows.js, which now merges definitions
    with statistics, but that is a tolerant reader over a producer that is
    returning less than it should.
  • "Start work" returns null when definitions is empty (workflows.jsx:104),
    so the form to start a workflow never renders on this composition at all.
    That is the more serious half: a whole feature is silently absent.

Expected

/api/workflows returns the workflow definitions from whichever process
serves it, or the UI service gets access to the registry the daemon builds.

Close reason

Closed on GitHub; syncing bead state


Imported from beads archie-core-3tij · GitHub #980 · type bug · priority P2 · created 2026-09-20 · closed 2026-09-26

Found while fixing archie-core-rcbf. `GET /api/workflows` on the dev stack returns `definitions: []` alongside `workflows: [{workflow: "implement", runs: 1, ...}]`, while the daemon logs "workflow registry built workflows=7" at startup. The registry lives in the daemon; the archie-ui process serving this endpoint does not have it, so it answers with an empty definition list. Two consequences in the UI: - The Per workflow empty state used to key off definitions alone, so the page claimed "No workflow runs yet" directly above the stage tables listing those runs. Fixed on the UI side in workflow-rows.js, which now merges definitions with statistics, but that is a tolerant reader over a producer that is returning less than it should. - "Start work" returns null when `definitions` is empty (`workflows.jsx:104`), so the form to start a workflow never renders on this composition at all. That is the more serious half: a whole feature is silently absent. ### Expected `/api/workflows` returns the workflow definitions from whichever process serves it, or the UI service gets access to the registry the daemon builds. ### Close reason Closed on GitHub; syncing bead state --- _Imported from beads `archie-core-3tij` · GitHub #980 · type bug · priority P2 · created 2026-09-20 · closed 2026-09-26_
sam added the mediumbug labels 2026-10-27 13:38:47 +00:00
sam self-assigned this 2026-10-27 13:38:47 +00:00
sam closed this issue 2026-10-27 13:38:47 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1041