langgenius / langgenius/dify

Answer Node not work in iteration (Also missing "message" event in SSE response )

Open
#38,867 4 comments 1 reaction 0 assignees View on GitHub
🐞 bug 1.16.0 project#dify
Dominant language
TypeScript
Stars
156k
Forks
24.6k
Avg merge
22h 9m
Merged PRs (30d)
610

Description

### 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] This is only for bug report, if you would like to ask a question, 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, otherwise it will be closed.
- [x] 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)
- [x] Please do not modify this template :) and fill in all the required fields.

### Dify version

1.16.0-rc1

### Cloud or Self Hosted

Self Hosted (Docker)

### Steps to reproduce

Image

### ✔️ Expected Behavior

The answer node within the iteration outputs correctly.

in 1.14.2, it works just fine, and /chat-messages api received "message" event in streaming mode, after upgrade to 1.16.0-rc1, only "message_end" event received which related to message

### ❌ Actual Behavior

look like the flow just ignored the answer node

Image

and "message" event is missing(see my chatflow events which has answer node in iteration)

Image

Contributor guide

Open the contributing guide

Research direction

Start at the /chat-messages streaming API and the workflow path for an Answer node inside an iteration; compare 1.14.2 with 1.16.0-rc1 to trace why only message_end is emitted. Done means the Answer node produces output and the streaming response includes the expected message event.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend-api-design
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.