Didn't wait for the branch to end completely

[BingZi-233]

Self Checks

• [X] This is only for bug report, if you would like to ask a question, please head to Discussions.
• [X] I have searched for existing issues search for existing issues, including closed ones.
• [X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• [X] Please do not modify this template :) and fill in all the required fields.

Dify version

0.11.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

✔️ Expected Behavior

Normal end

❌ Actual Behavior

Expected Behavior

[dosubot[bot]]

@BingZi-233 Hi there! I'm here to help you with any bugs, questions, or contributions you have for Dify. I'm a bot designed to assist you while waiting for a human maintainer. Let's tackle this issue together!

I found a similar closed issue where conversations were interrupted unexpectedly. The issue was related to the listen_timeout value in the ApplicationQueueManager class, which was set to 600 seconds. If the conversation lasted longer, it would be interrupted. This was addressed in a past update, and upgrading to version 0.5.7 resolved the issue ^[1].

Additionally, there was an open issue about workflows not producing output when using more than one web scraper. This was resolved by switching to custom web scraping tools ^[2].

You might want to check if these solutions are applicable to your situation or if there are any updates or configurations in your current version that could address the issue.

To continue talking to Dosu, mention @dosu.

[crazywoola]

Please provide a minimal DSL.