Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Cerrado
  • ¿Algo no está bien?
#646 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@lavaman131 ya está trabajando en esto.

Desde el 16/10/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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

Lenguaje dominante
TypeScript
Estrellas
406
Forks
24
Merge medio
12 h 42 min
PR fusionados (30 d)
416

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de githubnext/chopin

Todos los issues de githubnext/chopin

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.