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

API calls chatflow, and after returning "ping", no more stream return events are pulled. #16317

New Issue
Closed
opened 2026-02-21 19:25:37 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 19:25:37 -05:00
Owner
Copy Link
Copy Source

Originally created by @xiaoyesoso on GitHub (Aug 20, 2025).

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.7.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

The logs are still in the "Running" state：

Image

However, ChatFlow only runs a portion of the nodes and then stops：

Image

Note: There is an "HTTP request" node that takes a long time. I tried changing the input to make the "HTTP request" node take a shorter time, and the entire ChatFlow can be successfully executed.

With the same input (the "HTTP request" node takes a long time), it runs successfully directly on the web, but this problem occurs when calling the API.

✔️ Expected Behavior

Hopefully, calling ChatFlow using the API will succeed in the above situation.

❌ Actual Behavior

No response

Originally created by @xiaoyesoso on GitHub (Aug 20, 2025). ### 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.7.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce The logs are still in the "Running" state： <img width="1138" height="921" alt="Image" src="https://github.com/user-attachments/assets/386a8ee2-ee82-4da8-b4d1-530ee38b2df3" /> However, ChatFlow only runs a portion of the nodes and then stops： <img width="1134" height="486" alt="Image" src="https://github.com/user-attachments/assets/b859fb48-0b5f-4fef-b295-d35edcee3f18" /> Note: There is an "HTTP request" node that takes a long time. I tried changing the input to make the "HTTP request" node take a shorter time, and the entire ChatFlow can be successfully executed. With the same input (the "HTTP request" node takes a long time), it runs successfully directly on the web, but this problem occurs when calling the API. ### ✔️ Expected Behavior Hopefully, calling ChatFlow using the API will succeed in the above situation. ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:25:37 -05:00
yindo closed this issue 2026-02-21 19:25:37 -05:00
yindo commented 2026-02-21 19:25:38 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 20, 2025):

This issue is most likely caused by environment or deployment configuration rather than a bug in Dify itself. In self-hosted Docker setups, streaming support is always enabled, but reverse proxy buffering (like Nginx or Traefik), Docker networking, or WSGI/gunicorn settings can interfere with HTTP chunked responses or Server-Sent Events. The 'ping' event is a keep-alive, and if no further events are streamed, it usually means the response is being buffered or blocked by your deployment environment.

Check if you have any proxies or load balancers in front of Dify and make sure buffering is disabled for streaming endpoints. You can use curl --no-buffer or browser dev tools to watch the network response and confirm if chunks are arriving or being buffered. Also, verify that your HTTP request node isn't being delayed by something like a proxy (e.g., Squid), which has been known to cause long delays—disabling such proxies for HTTP requests can resolve this issue.

If you are using a model provider plugin, note that there is a known incompatibility between some plugins and the latest plugin daemon service in Dify 1.7.1, which can cause connection persistence issues. Switching to a different model provider or downgrading to Dify 1.4.1 may help if that's the case source, source, source.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Aug 20, 2025): <!-- Answer --> This issue is most likely caused by environment or deployment configuration rather than a bug in Dify itself. In self-hosted Docker setups, streaming support is always enabled, but reverse proxy buffering (like Nginx or Traefik), Docker networking, or WSGI/gunicorn settings can interfere with HTTP chunked responses or Server-Sent Events. The 'ping' event is a keep-alive, and if no further events are streamed, it usually means the response is being buffered or blocked by your deployment environment. Check if you have any proxies or load balancers in front of Dify and make sure buffering is disabled for streaming endpoints. You can use `curl --no-buffer` or browser dev tools to watch the network response and confirm if chunks are arriving or being buffered. Also, verify that your HTTP request node isn't being delayed by something like a proxy (e.g., Squid), which has been known to cause long delays—disabling such proxies for HTTP requests can resolve this issue. If you are using a model provider plugin, note that there is a known incompatibility between some plugins and the latest plugin daemon service in Dify 1.7.1, which can cause connection persistence issues. Switching to a different model provider or downgrading to Dify 1.4.1 may help if that's the case [source](https://github.com/langgenius/dify/issues/23311), [source](https://github.com/langgenius/dify-official-plugins/issues/1172), [source](https://github.com/langgenius/dify/issues/19104). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/4424f22a-1200-489b-b4d5-5a63541e7293?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/4424f22a-1200-489b-b4d5-5a63541e7293?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/4424f22a-1200-489b-b4d5-5a63541e7293?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/4424f22a-1200-489b-b4d5-5a63541e7293?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/4424f22a-1200-489b-b4d5-5a63541e7293?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/4424f22a-1200-489b-b4d5-5a63541e7293?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/4424f22a-1200-489b-b4d5-5a63541e7293?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/24268)
yindo commented 2026-02-21 19:25:38 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 21, 2025):

@crazywoola commented on GitHub (Aug 21, 2025): - https://github.com/langgenius/dify/issues/23654 - https://github.com/langgenius/dify/issues/23179 - https://github.com/langgenius/dify/issues/24143
yindo commented 2026-02-21 19:25:38 -05:00
Author
Owner
Copy Link
Copy Source

@1107186916 commented on GitHub (Sep 29, 2025):

Is it solved?

@1107186916 commented on GitHub (Sep 29, 2025): Is it solved?
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#16317
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?