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

step-by-step debugging of LLM nodes failed #2473

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

Originally created by @majestichou on GitHub (Apr 23, 2024).

Originally assigned to: @takatost on GitHub.

Self Checks

  • This is only for bug report, if you would like to ask a quesion, please head to Discussions.
  • 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).
  • Pleas do not modify this template :) and fill in all the required fields.

Dify version

0.6.4

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Workflow supports step-by-step debugging of nodes, where you can repetitively test whether the execution of the current node meets expectations.
However, when I step-by-step debugged the LLM node, the error happened.
I've selected the LLM node to test debug it. I typed in a prompt and clicked start run. However, the input is parsed as null, and the reply from the large model is not what I want.
Amazingly, I found that the example on Dify's website(https://docs.dify.ai/features/workflow/preview-and-run/step-test) also has this error. See the second image on this page for details.

✔️ Expected Behavior

step-by-step debugging of LLM nodes sucess

❌ Actual Behavior

step-by-step debugging of LLM nodes failed

Originally created by @majestichou on GitHub (Apr 23, 2024). Originally assigned to: @takatost on GitHub. ### Self Checks - [X] This is only for bug report, if you would like to ask a quesion, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [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] Pleas do not modify this template :) and fill in all the required fields. ### Dify version 0.6.4 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Workflow supports step-by-step debugging of nodes, where you can repetitively test whether the execution of the current node meets expectations. However, when I step-by-step debugged the LLM node, the error happened. I've selected the LLM node to test debug it. I typed in a prompt and clicked start run. However, the input is parsed as null, and the reply from the large model is not what I want. Amazingly, I found that the example on Dify's website(https://docs.dify.ai/features/workflow/preview-and-run/step-test) also has this error. See the second image on this page for details. ### ✔️ Expected Behavior step-by-step debugging of LLM nodes sucess ### ❌ Actual Behavior step-by-step debugging of LLM nodes failed
yindo added the 🐞 bug label 2026-02-21 17:46:14 -05:00
yindo closed this issue 2026-02-21 17:46:14 -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 🐞 bug
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#2473
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?