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

Enhance debugging target node in a workflow with a shortcut to use inputs from last test log #7281

New Issue
Closed
opened 2026-02-21 18:19:47 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:19:47 -05:00
Owner
Copy Link
Copy Source

Originally created by @GeorgeCaoJ on GitHub (Dec 18, 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).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Use case:
I have three sequential LLM nodes in a workflow, and I want to enhance the prompt for LLM2, which depends on the output from the previous LLM1 node.

Current approach:
There are two options for debugging the node:

  1. Testing from scratch: This option takes more tokens and time since the first LLM node is already working fine.
  2. Viewing the last test log, copying the inputs for LLM2, and pasting them into the debug form: This is my preferred option but could be made more convenient.

Desired improvement:
It would be great if there were a shortcut in the target node’s debug window to use the inputs from the last test log.

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @GeorgeCaoJ on GitHub (Dec 18, 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] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [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? Tell me about your story. **Use case:** I have three sequential LLM nodes in a workflow, and I want to enhance the prompt for LLM2, which depends on the output from the previous LLM1 node. **Current approach:** There are two options for debugging the node: 1. Testing from scratch: This option takes more tokens and time since the first LLM node is already working fine. 2. Viewing the last test log, copying the inputs for LLM2, and pasting them into the debug form: This is my preferred option but could be made more convenient. **Desired improvement:** It would be great if there were a shortcut in the target node’s debug window to use the inputs from the last test log. ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement🌊 feat:workflow labels 2026-02-21 18:19:47 -05:00
yindo closed this issue 2026-02-21 18:19:47 -05:00
yindo commented 2026-02-21 18:19:48 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 20, 2025):

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

Issue Summary

  • Enhancement proposal to add a shortcut in the debugging window for workflow's target node.
  • Feature aims to use inputs from the last test log automatically, easing debugging for sequential LLM nodes.
  • You mentioned not being interested in developing this feature yourself.
  • No further comments or activity have been recorded on this issue.

Next Steps

  • Is this issue still relevant to the latest version of the Dify repository? If so, please comment to keep the discussion open.
  • If there is no further activity, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Jan 20, 2025): Hi, @GeorgeCaoJ. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary** - Enhancement proposal to add a shortcut in the debugging window for workflow's target node. - Feature aims to use inputs from the last test log automatically, easing debugging for sequential LLM nodes. - You mentioned not being interested in developing this feature yourself. - No further comments or activity have been recorded on this issue. **Next Steps** - Is this issue still relevant to the latest version of the Dify repository? If so, please comment to keep the discussion open. - If there is no further activity, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
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 💪 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: langgenius/dify#7281
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?