Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When the conversation is interrupted by the page being closed, the large model gets stuck in an endless loop. #16934

Open
5 tasks done
v-49 opened this issue Mar 27, 2025 · 2 comments
Labels
🐞 bug Something isn't working 🤔 cant-reproduce We can not reproduce it or the information is limited

Comments

@v-49
Copy link

v-49 commented Mar 27, 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

Image
When the conversation is interrupted by the page being closed, the large model gets stuck in an endless loop.

how to reproduce it: open it on the explore; Send a question and then interrupt it when he is about to start by directly closing the page.

✔️ Expected Behavior

There is a timeout period; at least the large model won't run indefinitely like this; but in fact, the best situation is that after it is closed on the page, it can output normally, and at least the complete end can be seen in the log.

❌ Actual Behavior

llm endless running seem choked up

@dosubot dosubot bot added 🐞 bug Something isn't working 🤔 cant-reproduce We can not reproduce it or the information is limited labels Mar 27, 2025
Copy link

dosubot bot commented Mar 27, 2025

I couldn't find specific information on how Dify handles the lifecycle of a conversation when the page is closed abruptly or how it manages interruptions in the conversation workflow. However, there are mechanisms in place to handle interruptions or timeouts for long-running tasks, such as retry on failure, error handling, and environment configuration for managing timeouts [1].

Additionally, you might want to check the environment variables related to timeouts in your .env file, such as SSRF_DEFAULT_TIME_OUT, HTTP_REQUEST_MAX_CONNECT_TIMEOUT, and others, to ensure they are set appropriately to prevent the model from running indefinitely [2].

I found a similar unsolved discussion titled "What if my task keeps running and can't stop" that might be related to your issue [3].

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

@v-49
Copy link
Author

v-49 commented Mar 27, 2025

this bug is can be reproduced

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working 🤔 cant-reproduce We can not reproduce it or the information is limited
Projects
None yet
Development

No branches or pull requests

1 participant