Child Workflow status badge in Parent's Event History doesn't reflect child's current/final status
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 431
- Forks
- 179
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 71
Description
When viewing a Parent Workflow's Event History in the Temporal Web UI, the Child Workflow status badge shows "Started" even after the Child Workflow has been cancelled or completed. The badge only reflects the status at the time the event was recorded, not the child's current/final status.
Current Behavior
Parent Workflow starts a Child Workflow
Event History shows Start Child Workflow Execution Initiated with a "Started" badge
Child Workflow gets cancelled (or completes/fails)
Parent's Event History still shows "Started" badge for that child workflow event
Only when clicking into the Child Workflow directly does the user see the actual status ("Cancelled")
Expected Behavior
The Child Workflow status badge in the Parent's Event History should reflect the child's current/final status (e.g., "Cancelled", "Completed", "Failed"), or at minimum provide a visual indicator that the status shown is historical and may have changed
Can you explain if it's the correct behavior or not?.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the Temporal Web UI's Parent Workflow Event History and reproduce the case where a child is cancelled or completed after its start event. Trace how the Child Workflow status badge is sourced, then verify whether it can show the child's current or final status, or clearly identify the displayed status as historical. Done means the badge no longer misleadingly remains "Started" after the child reaches a final status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100