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

First Token Timeout for LLM Node Retry Mechanism #21742

New Issue
Open
opened 2026-02-21 20:14:07 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 20:14:07 -05:00
Owner
Copy Link
Copy Source

Originally created by @Nov1c444 on GitHub (Jan 18, 2026).

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.

When LLM services experience high latency or become unresponsive, the current retry mechanism cannot detect slow responses during streaming since it only triggers on actual errors. This feature adds a configurable "first token timeout" that monitors the time until the first token is received in streaming LLM responses. If the first token doesn't arrive within the specified timeout, an error is raised to trigger the retry mechanism, improving reliability for workflow execution.

2. Additional context or comments

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @Nov1c444 on GitHub (Jan 18, 2026). ### 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. When LLM services experience high latency or become unresponsive, the current retry mechanism cannot detect slow responses during streaming since it only triggers on actual errors. This feature adds a configurable "first token timeout" that monitors the time until the first token is received in streaming LLM responses. If the first token doesn't arrive within the specified timeout, an error is raised to trigger the retry mechanism, improving reliability for workflow execution. ### 2. Additional context or comments ### 3. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the 💪 enhancementstale labels 2026-02-21 20:14:07 -05:00
yindo commented 2026-02-21 20:14:07 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 19, 2026):

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

Issue Summary:

  • You requested a feature to add a configurable "first token timeout" for LLM streaming responses.
  • The goal is to trigger an error if the first token isn't received within a set time to improve retry mechanisms.
  • This feature aims to detect slow or unresponsive LLM services early, enhancing workflow reliability.
  • You expressed willingness to contribute to the implementation.
  • There has been no further activity or comments on this issue since it was opened.

Next Steps:

  • Please let me know if this feature is still relevant to 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.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Feb 19, 2026): Hi, @Nov1c444. 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 a feature to add a configurable "first token timeout" for LLM streaming responses. - The goal is to trigger an error if the first token isn't received within a set time to improve retry mechanisms. - This feature aims to detect slow or unresponsive LLM services early, enhancing workflow reliability. - You expressed willingness to contribute to the implementation. - There has been no further activity or comments on this issue since it was opened. **Next Steps:** - Please let me know if this feature is still relevant to 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. Thank you for your understanding and contribution!
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 stale 💪 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#21742
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?