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

The workflow execution time exceeds the time limit (about 650 seconds), and the result is not output #13330

New Issue
Closed
opened 2026-02-21 19:11:40 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 19:11:40 -05:00
Owner
Copy Link
Copy Source

Originally created by @birdOS1 on GitHub (Apr 24, 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

1.3.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

The background log shows that there are results
Image

✔️ Expected Behavior

The performance is consistent with the background log query

❌ Actual Behavior

No response

Originally created by @birdOS1 on GitHub (Apr 24, 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 1.3.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ![Image](https://github.com/user-attachments/assets/3412a313-8ce7-470e-834b-5f016c588712) The background log shows that there are results ![Image](https://github.com/user-attachments/assets/7415f1c8-f1d3-46df-99f9-0c763f9efee0) ### ✔️ Expected Behavior The performance is consistent with the background log query ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-21 19:11:40 -05:00
yindo commented 2026-02-21 19:11:41 -05:00
Author
Owner
Copy Link
Copy Source

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

https://github.com/langgenius/dify/blob/37e2f739091169eecc7c446d8232915bdaf6f895/docker/docker-compose.yaml#L351

@crazywoola commented on GitHub (Apr 24, 2025): https://github.com/langgenius/dify/blob/37e2f739091169eecc7c446d8232915bdaf6f895/docker/docker-compose.yaml#L351
yindo commented 2026-02-21 19:11:41 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 24, 2025):

There are a few similar discussions related to workflow execution timeouts in Dify:

  1. Results are not displayed due to timeout. Please refer to the logs to gather complete results. - This discussion is unsolved and was last updated on April 21, 2025 [1].
  2. Results are not displayed due to timeout in dify version v1.0.1 - This discussion is also unsolved and was last updated on March 21, 2025 [2].
  3. Workflow stop at 1200s - Another unsolved discussion, last updated on March 14, 2025 [3].

For your issue, you might want to check the timeout settings in your .env file. In Dify version 1.3.0, the default timeout setting for workflow execution is 60000 milliseconds [4]. You can extend this by configuring parameters like APP_MAX_EXECUTION_TIME and WORKFLOW_MAX_EXECUTION_TIME in your .env file to a higher value, such as 3600 seconds for 60 minutes of execution time [5]. After making changes, ensure to restart your Docker containers for the new settings to take effect.

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 (Apr 24, 2025): <!-- Answer --> There are a few similar discussions related to workflow execution timeouts in Dify: 1. [Results are not displayed due to timeout. Please refer to the logs to gather complete results.](https://github.com/langgenius/dify/discussions/18352) - This discussion is unsolved and was last updated on April 21, 2025 <sup>[[1]](https://github.com/langgenius/dify/discussions/18352)</sup>. 2. [Results are not displayed due to timeout in dify version v1.0.1](https://github.com/langgenius/dify/discussions/16474) - This discussion is also unsolved and was last updated on March 21, 2025 <sup>[[2]](https://github.com/langgenius/dify/discussions/16474)</sup>. 3. [Workflow stop at 1200s](https://github.com/langgenius/dify/discussions/15007) - Another unsolved discussion, last updated on March 14, 2025 <sup>[[3]](https://github.com/langgenius/dify/discussions/15007)</sup>. For your issue, you might want to check the timeout settings in your `.env` file. In Dify version 1.3.0, the default timeout setting for workflow execution is 60000 milliseconds <sup>[[4]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/environments.md)</sup>. You can extend this by configuring parameters like `APP_MAX_EXECUTION_TIME` and `WORKFLOW_MAX_EXECUTION_TIME` in your `.env` file to a higher value, such as 3600 seconds for 60 minutes of execution time <sup>[[5]](https://github.com/langgenius/dify/issues/14682)</sup>. After making changes, ensure to restart your Docker containers for the new settings to take effect. <!-- 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/f10a4aa5-b8f7-4fef-b35d-09e76d5ced83?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/f10a4aa5-b8f7-4fef-b35d-09e76d5ced83?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/f10a4aa5-b8f7-4fef-b35d-09e76d5ced83?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/f10a4aa5-b8f7-4fef-b35d-09e76d5ced83?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f10a4aa5-b8f7-4fef-b35d-09e76d5ced83?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/f10a4aa5-b8f7-4fef-b35d-09e76d5ced83?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f10a4aa5-b8f7-4fef-b35d-09e76d5ced83?feedback_type=other)</sup>
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
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#13330
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?