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

Can we set a timeout for flows? #21112

New Issue
Closed
opened 2026-02-21 20:10:49 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 20:10:49 -05:00
Owner
Copy Link
Copy Source

Originally created by @kyle0418 on GitHub (Dec 17, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Why can't we set a timeout parameter for flows? When a flow runs for too long, it becomes meaningless. Flows that run continuously consume system resources.

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @kyle0418 on GitHub (Dec 17, 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] 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] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. Why can't we set a timeout parameter for flows? When a flow runs for too long, it becomes meaningless. Flows that run continuously consume system resources. ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 20:10:49 -05:00
yindo closed this issue 2026-02-21 20:10:49 -05:00
yindo commented 2026-02-21 20:10:49 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Dec 17, 2025):

This one?

https://github.com/langgenius/dify/blob/b7649f61f842ce8c39c923f3898f8912450b7095/docker/.env.example#L140

@crazywoola commented on GitHub (Dec 17, 2025): This one? https://github.com/langgenius/dify/blob/b7649f61f842ce8c39c923f3898f8912450b7095/docker/.env.example#L140
yindo commented 2026-02-21 20:10:49 -05:00
Author
Owner
Copy Link
Copy Source

@kyle0418 commented on GitHub (Dec 17, 2025):

This one?

dify/docker/.env.example

Line 140 in b7649f6

APP_MAX_EXECUTION_TIME=1200

This appears to set a timeout for dify. But each flow's tasks are distinct, and their timeout requirements also differ. I want to set different timeouts for them, just like other workflow products do.

@kyle0418 commented on GitHub (Dec 17, 2025): > This one? > > [dify/docker/.env.example](https://github.com/langgenius/dify/blob/b7649f61f842ce8c39c923f3898f8912450b7095/docker/.env.example#L140) > > Line 140 in [b7649f6](/langgenius/dify/commit/b7649f61f842ce8c39c923f3898f8912450b7095) > > APP_MAX_EXECUTION_TIME=1200 This appears to set a timeout for dify. But each flow's tasks are distinct, and their timeout requirements also differ. I want to set different timeouts for them, just like other workflow products do.
yindo commented 2026-02-21 20:10:49 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Dec 26, 2025):

a parameter timeout, pass it the workflow ?

@fatelei commented on GitHub (Dec 26, 2025): a parameter timeout, pass it the workflow ?
yindo commented 2026-02-21 20:10:50 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 26, 2026):

Hi, @kyle0418. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested the ability to set individual timeout parameters for different flows to avoid indefinite execution and resource overuse.
  • Currently, the APP_MAX_EXECUTION_TIME setting applies globally, as noted by a contributor referencing the .env.example file.
  • You clarified the need for per-flow timeout customization similar to other workflow tools.
  • Another user suggested passing a timeout parameter directly to the workflow as a potential approach.
  • The issue remains unresolved with no implemented solution for granular timeout control.

Next Steps:

  • Please let me know if this feature is still relevant to your use case with the latest version of Dify by commenting on this issue.
  • If I do not hear back within 15 days, I will automatically close this issue to keep the backlog manageable.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Jan 26, 2026): Hi, @kyle0418. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested the ability to set individual timeout parameters for different flows to avoid indefinite execution and resource overuse. - Currently, the APP_MAX_EXECUTION_TIME setting applies globally, as noted by a contributor referencing the .env.example file. - You clarified the need for per-flow timeout customization similar to other workflow tools. - Another user suggested passing a timeout parameter directly to the workflow as a potential approach. - The issue remains unresolved with no implemented solution for granular timeout control. **Next Steps:** - Please let me know if this feature is still relevant to your use case with the latest version of Dify by commenting on this issue. - If I do not hear back within 15 days, I will automatically close this issue to keep the backlog manageable. Thank you for your understanding and contribution!
yindo commented 2026-02-21 20:10:50 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 3, 2026):

Hi @kyle0418, thanks for opening this issue.

Why this is being closed

This issue tracker is reserved for actionable bugs/tasks. This report looks like a usage question.

Next steps

Please use the community channels instead:

If this is actually a bug/task, please open a new issue with clear reproducible details.

Thanks for understanding and for supporting Dify.

@crazywoola commented on GitHub (Feb 3, 2026): Hi @kyle0418, thanks for opening this issue. ### Why this is being closed This issue tracker is reserved for actionable bugs/tasks. This report looks like a usage question. ### Next steps Please use the community channels instead: - https://forum.dify.ai/ - https://discord.com/invite/FngNHpbcY7 If this is actually a bug/task, please open a new issue with clear reproducible details. Thanks for understanding and for supporting Dify.
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 💪 enhancement
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#21112
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?