Issue: Direct Reply Node in Loop/Iteration Causes Errors, Stops After First Iteration, and Breaks Streaming (v1.61.1 & v1.17.1, Docker)
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- docker, typescript
调研方向
Start by reproducing the workflow with a Direct Reply node inside a loop or iteration using the Docker deployment and the affected versions. Trace the loop execution and streaming behavior from that node; the issue is done when execution completes all iterations, streams the first result, and raises no error.
由索引模型根据 Issue 内容生成。
描述
Self Checks
- I have read the Contributing Guide and Language Policy.
- 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, otherwise it will be closed.
- 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)
- Please do not modify this template :) and fill in all the required fields.
Dify version
1.16.1&1.17.1
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
Deploy the application using Docker with version 1.61.1 and/or 1.17.1.
Create a workflow that contains a loop/iteration.
Add a Direct Reply node inside the loop body and inside the iteration.
Execute the workflow and observe the behavior.
✔️ Expected Behavior
The Direct Reply node should work normally inside the loop body and inside the iteration.
Streaming output should be supported.
Execution should not throw an error or stop after only the first iteration.
The result of the first iteration should be streamed successfully.
❌ Actual Behavior
Adding a Direct Reply node inside the loop body and inside the iteration immediately causes an error, or execution stops after only the first iteration.
The result of the first iteration is not streamed.
This issue did not seem to occur before.
No specific logs are available for further analysis.
- 主要语言
- TypeScript
- 星标
- 157k
- 派生
- 24.7k
- 平均合并
- 22 小时 32 分钟
- 30 天内合并 PR
- 611
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
langgenius/dify 的其他 Issue
-
Annotation Reply: a stored score threshold of 0.0 is silently replaced with 1, disabling the feature 未关闭
难度 2/5 1-3 小时 新手友好度 88/100
langgenius/dify#42639 · 1 条评论 · 1 个 reaction ·
-
难度 2/5 1-3 小时 新手友好度 70/100
langgenius/dify#42468 · 1 条评论 · 1 个 reaction ·
-
🐞 bug
难度 2/5 1-3 小时 新手友好度 86/100
langgenius/dify#42446 · 1 个 reaction ·
-
难度 2/5 1-3 小时 新手友好度 88/100
langgenius/dify#42355 · 1 条评论 · 1 个 reaction ·
-
难度 2/5 1-3 小时 新手友好度 88/100
langgenius/dify#42350 · 1 条评论 · 1 个 reaction ·
相似的 Issue
-
calcite-components needs triage refactor
难度 2/5 1-3 小时 新手友好度 75/100
Esri/calcite-design-system#15203 ·
-
难度 2/5 1-3 小时 新手友好度 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
难度 1/5 1 小时以内 新手友好度 95/100
-
难度 2/5 1-3 小时 新手友好度 78/100
Automattic/studio#4908 ·
-
难度 2/5 1-3 小时 新手友好度 90/100