dify对话在思考过程中,如果切换了对话就会变成死循环 #15558

Closed
opened 2026-02-21 19:22:17 -05:00 by yindo · 1 comment
Owner

Originally created by @qiyaxiong on GitHub (Jul 22, 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.5

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

切换的话对话变成死循环

✔️ Expected Behavior

还是正常运行

Actual Behavior

No response

Originally created by @qiyaxiong on GitHub (Jul 22, 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.5 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 切换的话对话变成死循环 ### ✔️ Expected Behavior 还是正常运行 ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:22:17 -05:00
yindo closed this issue 2026-02-21 19:22:17 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Jul 22, 2025):

This issue is likely caused by a frontend state management problem when switching conversations while the AI is still responding. The code is designed to abort ongoing requests and reset state during a conversation switch, but rapid or unsynchronized actions can lead to race conditions or stuck states (dead loops) in the UI. Recent pull requests have improved conversation switching logic, but there is no explicit fix for this dead loop in the documentation or PRs.

I recommend testing with the latest version of Dify, as recent updates have improved related logic. If the problem persists, try collecting browser console logs and network traces when the dead loop occurs to help pinpoint the failure. If you can modify the code, consider adding more robust guard clauses or synchronization in the frontend (for example, in the handleStop or handleChangeConversation functions) to prevent race conditions. If you can share error messages or logs from the latest version, I can help investigate further.

Relevant code and PRs:

To reply, just mention @dosu.


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

@dosubot[bot] commented on GitHub (Jul 22, 2025): <!-- Answer --> This issue is likely caused by a frontend state management problem when switching conversations while the AI is still responding. The code is designed to abort ongoing requests and reset state during a conversation switch, but rapid or unsynchronized actions can lead to race conditions or stuck states (dead loops) in the UI. Recent pull requests have improved conversation switching logic, but there is no explicit fix for this dead loop in the documentation or PRs. I recommend testing with the latest version of Dify, as recent updates have improved related logic. If the problem persists, try collecting browser console logs and network traces when the dead loop occurs to help pinpoint the failure. If you can modify the code, consider adding more robust guard clauses or synchronization in the frontend (for example, in the `handleStop` or `handleChangeConversation` functions) to prevent race conditions. If you can share error messages or logs from the latest version, I can help investigate further. Relevant code and PRs: - [Recent PR improving conversation switching](https://github.com/langgenius/dify/pull/12348) - [Frontend logic for stopping/aborting on conversation switch](https://github.com/langgenius/dify/blob/e9c9c5d8f1129301f808552230ad6253af44310b/web/app/components/base/chat/chat/hooks.ts) <!-- 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/bc254277-46b5-476b-988b-9189e8ef5d4a?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/bc254277-46b5-476b-988b-9189e8ef5d4a?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/bc254277-46b5-476b-988b-9189e8ef5d4a?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/bc254277-46b5-476b-988b-9189e8ef5d4a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/bc254277-46b5-476b-988b-9189e8ef5d4a?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/bc254277-46b5-476b-988b-9189e8ef5d4a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/bc254277-46b5-476b-988b-9189e8ef5d4a?feedback_type=other)</sup>&nbsp;&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/22768)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#15558