Skip to content

When LLM nodes enable Error handling, streaming output fails. #15626

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
5 tasks done
MrXionGe opened this issue Mar 12, 2025 · 1 comment · Fixed by #13401
Closed
5 tasks done

When LLM nodes enable Error handling, streaming output fails. #15626

MrXionGe opened this issue Mar 12, 2025 · 1 comment · Fixed by #13401
Assignees
Labels
🐞 bug Something isn't working

Comments

@MrXionGe
Copy link

Self Checks

  • This is only for bug report, if you would like to ask a question, 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).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.15.2 | 0.15.3 | 1.0.0 | 1.0.1

Cloud or Self Hosted

Self Hosted (Docker), Cloud

Steps to reproduce

When LLM nodes enable Error handling, streaming output fails.

If the Error handling option is "fail branch", the streaming message will fail.

If the Error handling option is "none" or "default value", streaming messages will not be affected.

Image

step

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

@dosubot dosubot bot added the 🐞 bug Something isn't working label Mar 12, 2025
Copy link

dosubot bot commented Mar 12, 2025

The issue you're experiencing with streaming output failing when LLM nodes enable error handling with the "fail branch" option in Dify was previously identified in version 0.14.2. This problem was due to the LLM node's streaming output becoming blocking instead of streaming when using IF-ELSE conditions. It has been resolved in a recent update through PR #12105. Updating to the latest version of Dify that includes this fix should resolve the issue [1].

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants