Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

A stopped workflow stage should show its child stages as stopped too

Chiusa
  • Qualcosa non va?
#646 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@lavaman131 ci sta già lavorando.

Dal 16/10/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

When a workflow run stops, its run card in Chat shows the stopped stage as stopped, but the stages under it keep their last status, such as running or queued. The card then reads as though work is still going on inside a run that has ended.

Steps to reproduce

  1. Start a workflow run from a document's Planner whose stages have child stages, for example a stage that fans out into several sub-stages.
  2. While a parent stage and its children are running, stop the run. Ending the Planner's connection or deleting the document also stops it.
  3. Look at the run card in Chat (apps/web/src/chat/run-card.tsx).

Expected: every stage under a stopped stage shows stopped too, or a muted "not run" for ones that never started. The tree should agree with its parent, and no spinner should keep going under a stopped stage.

Actual: the parent shows stopped, while its children still show running or queued, sometimes with an active spinner.

Suggested fix

  • When the card renders a stage whose status is stopped, failed or cancelled, show each descendant that hasn't reached its own end state as stopped. A descendant that already finished (done or failed) keeps its own status.
  • Do this where the card builds its stage tree from the Planner's run report, so it applies however the report arrived (live update or reload). Optionally apply the same rule where the server stores the report (packages/protocol/chat.d.ts).
  • Add a unit test: a stopped parent with running, queued and done children renders stopped, stopped and done.
  • Add a design-audit plate: extend design-audit/plates/workflow-runs.tsx with a stopped run that has nested stages.

Assistant-workflow: inline
Assistant-duration: unmeasured
Assistant-verification: manual unavailable: UX feedback from lavaman131 after a run stopped mid-stage on the hosted instance; not reproduced locally
Co-authored-by: lavaman131

Lingua principale
TypeScript
Stelle
406
Fork
24
Merge medio
12h 42m
PR unite (30g)
416

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di githubnext/chopin

Tutte le issue di githubnext/chopin

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.