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

[Enhancement/Refactor] Improve debugging #15433

New Issue
Open
opened 2026-02-21 19:21:42 -05:00 by yindo · 8 comments
yindo commented 2026-02-21 19:21:42 -05:00
Owner
Copy Link
Copy Source

Originally created by @DavideDelbianco on GitHub (Jul 16, 2025).

Originally assigned to: @crazywoola on GitHub.

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 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.

  1. Whenever I try to debug, even though I have the "last run" explorer, I quite often need to manually copy inputs from a previous run from the logs.
    Having a button to copy the run values to make them the "last run" would be incredibly helpful.

  2. having a searchbox would make life easier instead of scrolling a tiny list of nodes

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 @DavideDelbianco on GitHub (Jul 16, 2025). Originally assigned to: @crazywoola on GitHub. ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [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. 1. Whenever I try to debug, even though I have the "last run" explorer, I quite often need to manually copy inputs from a previous run from the logs. Having a button to copy the run values to make them the "last run" would be incredibly helpful. 2. having a searchbox would make life easier instead of scrolling a tiny list of nodes ### 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 💪 enhancementrefactor labels 2026-02-21 19:21:42 -05:00
yindo commented 2026-02-21 19:21:43 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jul 16, 2025):

I think you just need to hit the "Play" button, it will automatically use previous values.

having a searchbox would make life easier instead of scrolling a tiny list of nodes

This sounds reasonable to me.

@crazywoola commented on GitHub (Jul 16, 2025): I think you just need to hit the "Play" button, it will automatically use previous values. > having a searchbox would make life easier instead of scrolling a tiny list of nodes This sounds reasonable to me.
yindo commented 2026-02-21 19:21:43 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Jul 17, 2025):

What I meant is to be able to "copy" the values from a specific run from the log history to the "last run".
This way you would be able to execute and debug with the same values from the log entry that you are inspecting.
A sort of replay of the logged run.

The play button uses last run values only

For example, here i have a FAIL

Image

I can inspect the log, but to reproduce the same run, i need to manually copy over the output values using variable inspector.
Having a replay button that copies every node to the workflow "last run" container, would make this task super easy

@DavideDelbianco commented on GitHub (Jul 17, 2025): What I meant is to be able to "copy" the values from a specific run from the log history to the "last run". This way you would be able to execute and debug with the same values from the log entry that you are inspecting. A sort of replay of the logged run. The play button uses last run values only For example, here i have a FAIL <img width="899" height="190" alt="Image" src="https://github.com/user-attachments/assets/37acd452-c3dc-44b8-a109-a54906e954f4" /> I can inspect the log, but to reproduce the same run, i need to manually copy over the output values using variable inspector. Having a replay button that copies every node to the workflow "last run" container, would make this task super easy
yindo commented 2026-02-21 19:21:43 -05:00
Author
Owner
Copy Link
Copy Source

@ZeroZ-lab commented on GitHub (Jul 17, 2025):

hi, @crazywoola ,I also really need the search node function. Please review if my creation is acceptable. I am very much looking forward to your feedback. I really need it.

@ZeroZ-lab commented on GitHub (Jul 17, 2025): hi, @crazywoola ,I also really need the search node function. Please review if my creation is acceptable. I am very much looking forward to your feedback. I really need it.
yindo commented 2026-02-21 19:21:43 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jul 31, 2025):

@ZeroZ-lab sent a PR regarding 'having a searchbox would make life easier instead of scrolling a tiny list of nodes'. I will make some changes from our designer's suggestion to this. @DavideDelbianco

Whenever I try to debug, even though I have the "last run" explorer, I quite often need to manually copy inputs from a previous run from the logs.
Having a button to copy the run values to make them the "last run" would be incredibly helpful.

I will try to reach out to our PM about this. This won't be very hard to implement.

@crazywoola commented on GitHub (Jul 31, 2025): @ZeroZ-lab sent a PR regarding 'having a searchbox would make life easier instead of scrolling a tiny list of nodes'. I will make some changes from our designer's suggestion to this. @DavideDelbianco > Whenever I try to debug, even though I have the "last run" explorer, I quite often need to manually copy inputs from a previous run from the logs. Having a button to copy the run values to make them the "last run" would be incredibly helpful. I will try to reach out to our PM about this. This won't be very hard to implement.
yindo commented 2026-02-21 19:21:43 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Aug 1, 2025):

@crazywoola @ZeroZ-lab
The feature you introduced is really helpful, just like the one that wanted to introduce a graph node search functionality.
But the section I am talking about, that need a search box, is this one:

Image
@DavideDelbianco commented on GitHub (Aug 1, 2025): @crazywoola @ZeroZ-lab The feature you introduced is really helpful, just like the one that wanted to introduce a graph node search functionality. But the section I am talking about, that need a search box, is this one: <img width="1270" height="408" alt="Image" src="https://github.com/user-attachments/assets/1af55f8b-e6d8-4050-8d24-52e35a9f0001" />
yindo commented 2026-02-21 19:21:43 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 5, 2025):

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

Issue Summary:

  • You suggested adding a button to copy inputs from specific previous runs into the "last run" explorer to facilitate replay and reuse.
  • You also requested a search box to quickly find nodes in a particular UI section for better usability.
  • crazywoola confirmed the play button currently uses only the last run values and supports the search box idea.
  • A PR from ZeroZ-lab for node search is under refinement.
  • crazywoola plans to discuss the copy-run-values feature with the PM, noting it should be straightforward.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open.
  • Otherwise, this issue will be automatically closed in 15 days.

Thanks for your understanding and contribution!

@dosubot[bot] commented on GitHub (Sep 5, 2025): Hi, @DavideDelbianco. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You suggested adding a button to copy inputs from specific previous runs into the "last run" explorer to facilitate replay and reuse. - You also requested a search box to quickly find nodes in a particular UI section for better usability. - crazywoola confirmed the play button currently uses only the last run values and supports the search box idea. - A PR from ZeroZ-lab for node search is under refinement. - crazywoola plans to discuss the copy-run-values feature with the PM, noting it should be straightforward. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open. - Otherwise, this issue will be automatically closed in 15 days. Thanks for your understanding and contribution!
yindo commented 2026-02-21 19:21:43 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Sep 5, 2025):

Still relevant

@DavideDelbianco commented on GitHub (Sep 5, 2025): Still relevant
yindo commented 2026-02-21 19:21:44 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 5, 2025):

@crazywoola The user confirmed this issue is still relevant regarding the copy inputs from previous runs and the search box for nodes. Could you please assist with the next steps?

@dosubot[bot] commented on GitHub (Sep 5, 2025): @crazywoola The user confirmed this issue is still relevant regarding the copy inputs from previous runs and the search box for nodes. Could you please assist with the next steps?
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 refactor 💪 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#15433
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?