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

The DeepSeek thinking process is stuck. #8646

New Issue
Closed
opened 2026-02-21 18:26:50 -05:00 by yindo · 9 comments
yindo commented 2026-02-21 18:26:50 -05:00
Owner
Copy Link
Copy Source

Originally created by @TaylorSwift5201314 on GitHub (Feb 26, 2025).

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Ask for help：
DeepSeek has been stuck in deep thinking and has not been outputting for a long time. The environment used is: Dify + Ollama (DeepSeek: 32B). Checking the output, it was found that the data has ended.

Image

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

Image

DeepSeek has been stuck in deep thinking and has not been outputting for a long time. The environment used is: Dify + Ollama (DeepSeek: 32B). Checking the output, it was found that the data has ended.

Image

Originally created by @TaylorSwift5201314 on GitHub (Feb 26, 2025). ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.15.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Ask for help： DeepSeek has been stuck in deep thinking and has not been outputting for a long time. The environment used is: Dify + Ollama (DeepSeek: 32B). Checking the output, it was found that the data has ended. ![Image](https://github.com/user-attachments/assets/9855f068-2b03-4842-bb0d-af52593028b0) ![Image](https://github.com/user-attachments/assets/3418f802-b3d4-48a6-aa17-33b516287e8f) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior ![Image](https://github.com/user-attachments/assets/e7b874b3-6eea-4b37-9e0c-0f9d6f242f6c) DeepSeek has been stuck in deep thinking and has not been outputting for a long time. The environment used is: Dify + Ollama (DeepSeek: 32B). Checking the output, it was found that the data has ended. ![Image](https://github.com/user-attachments/assets/40038cc1-617f-4a28-a26d-0b6e578c1b39)
yindo added the 🤔 cant-reproduce label 2026-02-21 18:26:50 -05:00
yindo closed this issue 2026-02-21 18:26:50 -05:00
yindo commented 2026-02-21 18:26:50 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 26, 2025):

@TaylorSwift5201314 Hello! I'm here to help you with any bugs, questions, or contributions you have for Dify. I'll assist you while we wait for a human maintainer.

A similar issue has been discussed in the Dify repository, where DeepSeek was stuck in deep thinking and not outputting results in the Dify + Ollama (DeepSeek: 32B) environment. Here are some potential solutions to consider:

  1. API Connection Issues: If you are running Dify and Ollama inside Docker, ensure that the network configuration allows proper access. Use 'host.docker.internal' instead of 'localhost' in the Ollama host address configuration, such as http://host.docker.internal:11434 [1].

  2. Service Status Monitoring: Check the service status at status.deepseek.com to see if there are any ongoing issues with the DeepSeek service [2].

  3. Load Balancing and Error Handling: Implement load balancing or use an error handling node within your workflow to manage errors effectively [2].

These steps should help address the issue of DeepSeek being stuck in deep thinking.

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

@dosubot[bot] commented on GitHub (Feb 26, 2025): <!-- Greeting --> @TaylorSwift5201314 Hello! I'm here to help you with any bugs, questions, or contributions you have for Dify. I'll assist you while we wait for a human maintainer. <!-- Answer --> A similar issue has been discussed in the Dify repository, where DeepSeek was stuck in deep thinking and not outputting results in the Dify + Ollama (DeepSeek: 32B) environment. Here are some potential solutions to consider: 1. **API Connection Issues**: If you are running Dify and Ollama inside Docker, ensure that the network configuration allows proper access. Use 'host.docker.internal' instead of 'localhost' in the Ollama host address configuration, such as `http://host.docker.internal:11434` <sup>[[1]](https://github.com/langgenius/dify/issues/14289)</sup>. 2. **Service Status Monitoring**: Check the service status at status.deepseek.com to see if there are any ongoing issues with the DeepSeek service <sup>[[2]](https://github.com/langgenius/dify/issues/13258)</sup>. 3. **Load Balancing and Error Handling**: Implement load balancing or use an error handling node within your workflow to manage errors effectively <sup>[[2]](https://github.com/langgenius/dify/issues/13258)</sup>. These steps should help address the issue of DeepSeek being stuck in deep thinking. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/f7e6a926-3b99-41ff-a974-fc9f4e99585a?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/f7e6a926-3b99-41ff-a974-fc9f4e99585a?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/f7e6a926-3b99-41ff-a974-fc9f4e99585a?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/f7e6a926-3b99-41ff-a974-fc9f4e99585a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f7e6a926-3b99-41ff-a974-fc9f4e99585a?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/f7e6a926-3b99-41ff-a974-fc9f4e99585a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f7e6a926-3b99-41ff-a974-fc9f4e99585a?feedback_type=other)</sup>
yindo commented 2026-02-21 18:26:50 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 26, 2025):

It should be fixed in the latest branch. And you will not see the time duration in v0.15.3. So do what's your version number?

@crazywoola commented on GitHub (Feb 26, 2025): It should be fixed in the latest branch. And you will not see the time duration in v0.15.3. So do what's your version number?
yindo commented 2026-02-21 18:26:50 -05:00
Author
Owner
Copy Link
Copy Source

@mu-dan commented on GitHub (Feb 26, 2025):

我的agent也是这种问题，也不调用工具，就直接结束了（版本是：

Image

）

Image

@mu-dan commented on GitHub (Feb 26, 2025): 我的agent也是这种问题，也不调用工具，就直接结束了（版本是： ![Image](https://github.com/user-attachments/assets/779acd26-daab-42a5-aa80-c4dbca12526f) ） ![Image](https://github.com/user-attachments/assets/a8bafa88-b515-4b4e-8cd3-c1b942611e40)
yindo commented 2026-02-21 18:26:50 -05:00
Author
Owner
Copy Link
Copy Source

@TaylorSwift5201314 commented on GitHub (Feb 27, 2025):

Previously, I only upgraded the API. Now, I have upgraded both the web and API to version v0.15.3, but the lag issue still persists. The deepseek thinking process ends prematurely. The first time it works normally, but when it comes to the second sentence and needs to combine the context, it always gets stuck.

@TaylorSwift5201314 commented on GitHub (Feb 27, 2025): Previously, I only upgraded the API. Now, I have upgraded both the web and API to version v0.15.3, but the lag issue still persists. The deepseek thinking process ends prematurely. The first time it works normally, but when it comes to the second sentence and needs to combine the context, it always gets stuck.
yindo commented 2026-02-21 18:26:50 -05:00
Author
Owner
Copy Link
Copy Source

@TaylorSwift5201314 commented on GitHub (Feb 27, 2025):

The issue still persists. The second model output prematurely "message_end", and the output stopped. The environment used is:
Dify: V0.15.3
Ollama: V0.5.12
DeepSeek: All products in the series have experienced the premature stoppage of the second thought process output.
Image

Image

@TaylorSwift5201314 commented on GitHub (Feb 27, 2025): The issue still persists. The second model output prematurely "message_end", and the output stopped. The environment used is: Dify: V0.15.3 Ollama: V0.5.12 DeepSeek: All products in the series have experienced the premature stoppage of the second thought process output. ![Image](https://github.com/user-attachments/assets/7f551c66-2cee-406f-ae13-9db98fcd33c3) ![Image](https://github.com/user-attachments/assets/6f6df54e-3cf4-41f6-ab92-d77d8c3953f4)
yindo commented 2026-02-21 18:26:50 -05:00
Author
Owner
Copy Link
Copy Source

@Yangjh71 commented on GitHub (Mar 2, 2025):

Encountered the same problem. It occurs very frequently, almost rendering it unusable.

@Yangjh71 commented on GitHub (Mar 2, 2025): Encountered the same problem. It occurs very frequently, almost rendering it unusable.
yindo commented 2026-02-21 18:26:50 -05:00
Author
Owner
Copy Link
Copy Source

@xiayouran commented on GitHub (Mar 2, 2025):

same issue.

LLM node output：

Image

API output：

Image

@xiayouran commented on GitHub (Mar 2, 2025): same issue. LLM node output： ![Image](https://github.com/user-attachments/assets/97e4ecc4-f708-4dce-8424-ef57b768281a) API output： ![Image](https://github.com/user-attachments/assets/a3235f7d-6f4a-4c48-a9be-39304c5cb9d5)
yindo commented 2026-02-21 18:26:51 -05:00
Author
Owner
Copy Link
Copy Source

@Yangjh71 commented on GitHub (Mar 2, 2025):

Encountered the same problem. It occurs very frequently, almost rendering it unusable.

It seems that this issue does not occur when I do not use the knowledge base

@Yangjh71 commented on GitHub (Mar 2, 2025): > Encountered the same problem. It occurs very frequently, almost rendering it unusable. It seems that this issue does not occur when I do not use the knowledge base
yindo commented 2026-02-21 18:26:51 -05:00
Author
Owner
Copy Link
Copy Source

@colstars commented on GitHub (Mar 17, 2025):

Get this problem too,It occurs very frequently ,my version is 1.0.1

@colstars commented on GitHub (Mar 17, 2025): Get this problem too,It occurs very frequently ,my version is 1.0.1
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 🤔 cant-reproduce
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#8646
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?