run-llama/workflows-py
1
0
Fork 0
mirror of https://github.com/run-llama/workflows-py.git synced 2026-07-19 08:46:21 -04:00
Code Issues 18 Packages Projects Releases 10 Wiki Activity

Workflow step spans are no longer parented under workflow run span since v2.14.0 #34

New Issue
Closed
opened 2026-02-16 02:16:13 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 02:16:13 -05:00
Owner
Copy Link
Copy Source

Originally created by @schelv on GitHub (Feb 13, 2026).

Starting from llama-index-workflows==2.14.0, workflow step spans are no longer grouped under their corresponding workflow run span in Arize Phoenix.

In v2.13.1, all step spans are correctly nested under their corresponding workflow run span (see screenshot, bottom section).
In v2.14.0, the step spans appear as separate top-level spans instead of being parented to the workflow run (see screenshot, top section).

Image

Tracing is still emitted, but span parent relationships appear to be broken.

In 2.13.1, the Context object memory address (0x...) remains constant across workflow steps. In 2.14.0, a new Context object appears per step (different 0x...), which may indicate a change in context propagation.

Reproduction

  • Works as expected in: 2.13.1
  • Broken in: 2.14.0
  • Observed in Arize Phoenix
Originally created by @schelv on GitHub (Feb 13, 2026). Starting from `llama-index-workflows==2.14.0`, workflow step spans are no longer grouped under their corresponding workflow run span in Arize Phoenix. In `v2.13.1`, all step spans are correctly nested under their corresponding workflow run span (see screenshot, bottom section). In `v2.14.0`, the step spans appear as separate top-level spans instead of being parented to the workflow run (see screenshot, top section). <img width="1072" height="565" alt="Image" src="https://github.com/user-attachments/assets/bf7b7e2e-1fab-46d8-a530-e84503abe251" /> Tracing is still emitted, but span parent relationships appear to be broken. In `2.13.1`, the `Context` object memory address (`0x...`) remains constant across workflow steps. In `2.14.0`, a new `Context` object appears per step (different `0x...`), which may indicate a change in context propagation. **Reproduction** * Works as expected in: `2.13.1` * Broken in: `2.14.0` * Observed in Arize Phoenix
yindo closed this issue 2026-02-16 02:16:13 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
enhancement
good first issue
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/workflows-py#34
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?