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

Results are not displayed due to timeout. Please refer to the logs to gather complete results. #7459

New Issue
Closed
opened 2026-02-21 18:20:42 -05:00 by yindo · 6 comments
yindo commented 2026-02-21 18:20:42 -05:00
Owner
Copy Link
Copy Source

Originally created by @canbyme on GitHub (Dec 30, 2024).

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

Read already

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Dify V0.14.2

By iteratively writing and outputting a long document, the test was successfully executed on the layout page, but after publishing, there was no output result on the user page, resulting in an error: Results are not displayed due to timeout. Please refer to the logs to gather complete results.

901104c743d8f43df502af217552caf 249581f4d34a228fc30a581624c0da0

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @canbyme on GitHub (Dec 30, 2024). ### 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 Read already ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Dify V0.14.2 By iteratively writing and outputting a long document, the test was successfully executed on the layout page, but after publishing, there was no output result on the user page, resulting in an error: Results are not displayed due to timeout. Please refer to the logs to gather complete results. <img width="349" alt="901104c743d8f43df502af217552caf" src="https://github.com/user-attachments/assets/506acc5d-9974-46d2-879b-9724b6fbe656" /> <img width="1146" alt="249581f4d34a228fc30a581624c0da0" src="https://github.com/user-attachments/assets/50a50c38-627e-48da-b539-3168587d3672" /> ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:20:42 -05:00
yindo closed this issue 2026-02-21 18:20:42 -05:00
yindo commented 2026-02-21 18:20:43 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 30, 2024):

@canbyme Hello! I'm here to help you with any bugs, questions, or contributions while you wait for a human maintainer. I'm looking forward to assisting you!

I found a similar open issue titled "ai completion result not shown" which might be related to the problem you're experiencing [1]. Additionally, there is a discussion thread titled "The frontend cannot show the generated text by llm" that remains unsolved [2].

For the timeout issue you're encountering, consider the following:

  1. Adjust Timeout Settings: You can modify the TEXT_GENERATION_TIMEOUT_MS in the .env file to increase the timeout duration for text generation processes. The default is 60 seconds, but you may need to extend this to accommodate longer processing times [3].

  2. Check Worker Process Configuration: Ensure that your worker processes are not being terminated prematurely due to timeouts. You might need to adjust the GUNICORN_TIMEOUT setting, which has a default of 200 seconds, but a recommended value of 360 seconds for longer tasks [3].

  3. Rate Limiting: If you're using an external embedding service, ensure that you're not hitting rate limits, which can cause timeouts. Implementing rate limiting or backoff strategies might help [4].

Reviewing the logs as suggested in the error message can provide more specific insights into what might be causing the timeout.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@dosubot[bot] commented on GitHub (Dec 30, 2024): <!-- Greeting --> @canbyme Hello! I'm here to help you with any bugs, questions, or contributions while you wait for a human maintainer. I'm looking forward to assisting you! <!-- Answer --> I found a similar open issue titled "ai completion result not shown" which might be related to the problem you're experiencing <sup>[[1]](https://github.com/langgenius/dify/issues/6874)</sup>. Additionally, there is a discussion thread titled "The frontend cannot show the generated text by llm" that remains unsolved <sup>[[2]](https://github.com/langgenius/dify/discussions/4081)</sup>. For the timeout issue you're encountering, consider the following: 1. **Adjust Timeout Settings**: You can modify the `TEXT_GENERATION_TIMEOUT_MS` in the `.env` file to increase the timeout duration for text generation processes. The default is 60 seconds, but you may need to extend this to accommodate longer processing times <sup>[[3]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/environments.md)</sup>. 2. **Check Worker Process Configuration**: Ensure that your worker processes are not being terminated prematurely due to timeouts. You might need to adjust the `GUNICORN_TIMEOUT` setting, which has a default of 200 seconds, but a recommended value of 360 seconds for longer tasks <sup>[[3]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/environments.md)</sup>. 3. **Rate Limiting**: If you're using an external embedding service, ensure that you're not hitting rate limits, which can cause timeouts. Implementing rate limiting or backoff strategies might help <sup>[[4]](https://github.com/langgenius/dify/issues/11694)</sup>. Reviewing the logs as suggested in the error message can provide more specific insights into what might be causing the timeout. <!-- 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/217a95d8-0f6b-408d-813c-cf43286d30e1?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/217a95d8-0f6b-408d-813c-cf43286d30e1?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/217a95d8-0f6b-408d-813c-cf43286d30e1?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/217a95d8-0f6b-408d-813c-cf43286d30e1?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/217a95d8-0f6b-408d-813c-cf43286d30e1?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/217a95d8-0f6b-408d-813c-cf43286d30e1?feedback_type=other)</sup>
yindo commented 2026-02-21 18:20:43 -05:00
Author
Owner
Copy Link
Copy Source

@canbyme commented on GitHub (Dec 30, 2024):

According to your reply, I have changed the default value of 60 seconds to 600 seconds (10 minutes) in the. env file. The problem has been resolved. Thank you very much!

@canbyme commented on GitHub (Dec 30, 2024): According to your reply, I have changed the default value of 60 seconds to 600 seconds (10 minutes) in the. env file. The problem has been resolved. Thank you very much!
yindo commented 2026-02-21 18:20:43 -05:00
Author
Owner
Copy Link
Copy Source

@myamamam commented on GitHub (Mar 12, 2025):

it doesn't work

@myamamam commented on GitHub (Mar 12, 2025): it doesn't work
yindo commented 2026-02-21 18:20:43 -05:00
Author
Owner
Copy Link
Copy Source

@shuai-huaman commented on GitHub (Apr 8, 2025):

If it is a cloud service, how to modify this timeout period

@shuai-huaman commented on GitHub (Apr 8, 2025): If it is a cloud service, how to modify this timeout period
yindo commented 2026-02-21 18:20:43 -05:00
Author
Owner
Copy Link
Copy Source

@eunicexi88 commented on GitHub (Apr 24, 2025):

If it is a cloud service, how to modify this timeout period

I have the exactly same question.

@eunicexi88 commented on GitHub (Apr 24, 2025): > If it is a cloud service, how to modify this timeout period I have the exactly same question.
yindo commented 2026-02-21 18:20:43 -05:00
Author
Owner
Copy Link
Copy Source

@yuquant commented on GitHub (Aug 7, 2025):

In dify 1.7.1, raise another error in “Run Batch” page,I can't find any config related to this in .env : [models] Connection Error, HTTPConnectionPool(host='192.168.1.213', port=21434): Read timed out. (read timeout=300)

@yuquant commented on GitHub (Aug 7, 2025): In dify 1.7.1, raise another error in “Run Batch” page,I can't find any config related to this in .env : [models] Connection Error, HTTPConnectionPool(host='192.168.1.213', port=21434): Read timed out. (read timeout=300)
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#7459
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?