langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

工作流节点创建和调试时保存输入输出变量 #3444

New Issue
Closed
opened 2026-02-21 17:57:52 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:57:52 -05:00
Owner
Copy Link
Copy Source

Originally created by @wobure123 on GitHub (May 17, 2024).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing?

When debugging a newly created workflow, I have to re-enter the input every time. Debugging a single node also requires entering input variables repeatedly, and it needs to be adapted to consider the output of the previous node. Debugging efficiency is not high.

2. Describe the feature you'd like to see

Personally, I believe the following design can greatly facilitate debugging and exploration:

  1. Save the input of each node from the last test run.
  2. Can the testing of connected nodes be designed to run in a sequential cell debugging manner similar to Jupyter Notebook, where the next node can read variables from previous nodes?
  3. Can a button be added to run from the start to the current test node?

3. How will this feature improve your workflow or experience?

Based on real-time node operation information, facilitate immersive design for current and next node input-output adaptation, as well as saving repetitive calls to LLM and other tool APIs.

4. Additional context or comments

Make debugging workflows as straightforward as debugging ipynb code~

5. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @wobure123 on GitHub (May 17, 2024). ### Self Checks - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? When debugging a newly created workflow, I have to re-enter the input every time. Debugging a single node also requires entering input variables repeatedly, and it needs to be adapted to consider the output of the previous node. Debugging efficiency is not high. ### 2. Describe the feature you'd like to see Personally, I believe the following design can greatly facilitate debugging and exploration: 1. Save the input of each node from the last test run. 2. Can the testing of connected nodes be designed to run in a sequential cell debugging manner similar to Jupyter Notebook, where the next node can read variables from previous nodes? 3. Can a button be added to run from the start to the current test node? ### 3. How will this feature improve your workflow or experience? Based on real-time node operation information, facilitate immersive design for current and next node input-output adaptation, as well as saving repetitive calls to LLM and other tool APIs. ### 4. Additional context or comments Make debugging workflows as straightforward as debugging ipynb code~ ### 5. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 🌊 feat:workflow label 2026-02-21 17:57:52 -05:00
yindo closed this issue 2026-02-21 17:57:52 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🌊 feat:workflow
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: langgenius/dify#3444
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?