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

[Feature Request]: Ability for draw_all_possible_flows, draw_most_recent_execution to draw nested workflows steps #2

New Issue
Open
opened 2026-02-16 02:16:02 -05:00 by yindo · 5 comments
yindo commented 2026-02-16 02:16:02 -05:00
Owner
Copy Link
Copy Source

Originally created by @CharlyJazz on GitHub (Feb 10, 2025).

Feature Description

  • Currently as the doc says draw_most_recent_execution, draw_most_recent_execution do not draw nested workflows steps but this should be super awesome!
  • I think we can save the nested workflow instance on the Context and use it to render the nested information, right?

On a Step:

await ctx.set('nested_workflow', nested_workflow)
await nested_workflow.run()

On StopEvent:

nested_workflow_instance: NestedWorkflow = await ctx.get('nested_workflow')
draw_all_possible_flows(workflow, filename="example.html", nested_workflows=[nested_workflow_instance])

Reason

I don't know the technical reasons behind!

Value of Feature

No response

Originally created by @CharlyJazz on GitHub (Feb 10, 2025). ### Feature Description - Currently as the doc says draw_most_recent_execution, draw_most_recent_execution do not draw nested workflows steps but this should be super awesome! - I think we can save the nested workflow instance on the Context and use it to render the nested information, right? On a Step: ```python await ctx.set('nested_workflow', nested_workflow) await nested_workflow.run() ``` On StopEvent: ```python nested_workflow_instance: NestedWorkflow = await ctx.get('nested_workflow') draw_all_possible_flows(workflow, filename="example.html", nested_workflows=[nested_workflow_instance]) ``` ### Reason I don't know the technical reasons behind! ### Value of Feature _No response_
yindo added the enhancement label 2026-02-16 02:16:02 -05:00
yindo commented 2026-02-16 02:16:02 -05:00
Author
Owner
Copy Link
Copy Source

@logan-markewich commented on GitHub (Feb 10, 2025):

@CharlyJazz there is the injection syntax described here
https://docs.llamaindex.ai/en/stable/understanding/workflows/nested/

Using that, with the nest workflow officially attached to the parent workflow, it might be possible to do

@logan-markewich commented on GitHub (Feb 10, 2025): @CharlyJazz there is the injection syntax described here https://docs.llamaindex.ai/en/stable/understanding/workflows/nested/ Using that, with the nest workflow officially attached to the parent workflow, it might be possible to do
yindo commented 2026-02-16 02:16:02 -05:00
Author
Owner
Copy Link
Copy Source

@CharlyJazz commented on GitHub (Feb 10, 2025):

Sorry I am a little slow, thanks for the answer so fast!!!
Is this what you mean? https://docs.llamaindex.ai/en/stable/understanding/workflows/nested/#default-workflows

@CharlyJazz commented on GitHub (Feb 10, 2025): Sorry I am a little slow, thanks for the answer so fast!!! Is this what you mean? https://docs.llamaindex.ai/en/stable/understanding/workflows/nested/#default-workflows
yindo commented 2026-02-16 02:16:02 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 12, 2025):

Hi, @CharlyJazz. I'm Dosu, and I'm helping the LlamaIndex team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • Proposed feature enhancement to improve visualization of nested workflow steps.
  • Enhancement involves saving nested workflow instance in context for better rendering.
  • Logan-markewich suggested using injection syntax from documentation for nested workflows.
  • You acknowledged the suggestion and agreed to explore the documentation further.

Next Steps:

  • Please confirm if this issue is still relevant to the latest version of the LlamaIndex repository by commenting here.
  • If no further updates are provided, the issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (May 12, 2025): Hi, @CharlyJazz. I'm [Dosu](https://dosu.dev), and I'm helping the LlamaIndex team manage their backlog. I'm marking this issue as stale. **Issue Summary:** - Proposed feature enhancement to improve visualization of nested workflow steps. - Enhancement involves saving nested workflow instance in context for better rendering. - Logan-markewich suggested using injection syntax from documentation for nested workflows. - You acknowledged the suggestion and agreed to explore the documentation further. **Next Steps:** - Please confirm if this issue is still relevant to the latest version of the LlamaIndex repository by commenting here. - If no further updates are provided, the issue will be automatically closed in 7 days. Thank you for your understanding and contribution!
yindo commented 2026-02-16 02:16:03 -05:00
Author
Owner
Copy Link
Copy Source

@CharlyJazz commented on GitHub (May 14, 2025):

Yes, this issues is not still addressed

@CharlyJazz commented on GitHub (May 14, 2025): Yes, this issues is not still addressed
yindo commented 2026-02-16 02:16:03 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 14, 2025):

@logan-markewich, the user @CharlyJazz has confirmed that the issue regarding the enhancement for visualizing nested workflow steps is still relevant and needs attention. Could you please assist them with this?

@dosubot[bot] commented on GitHub (May 14, 2025): @logan-markewich, the user @CharlyJazz has confirmed that the issue regarding the enhancement for visualizing nested workflow steps is still relevant and needs attention. Could you please assist them with this?
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 enhancement
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#2
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?