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

better error handling for professional flows #7036

New Issue
Closed
opened 2026-02-21 18:18:33 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:18:33 -05:00
Owner
Copy Link
Copy Source

Originally created by @lucaseatp on GitHub (Dec 3, 2024).

Self Checks

  • 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.

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

dify is a great tool, but it lacks one crucial thing for production: better error handling.

Straightforward things make a huge difference, like, when anthropic gives you a 529 error (overloaded), wait 15 seconds and try again, maybe you can do it 3 or 5 times.

if it doesn't work, we should have the option to choose another AI model to handle this data.

really simple things, but they make a huge difference to avoid errors in production flows.

and that's just for llm nodes... error handling should be a feature anytime soon

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 @lucaseatp on GitHub (Dec 3, 2024). ### Self Checks - [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. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. dify is a great tool, but it lacks one crucial thing for production: better error handling. Straightforward things make a huge difference, like, when anthropic gives you a 529 error (overloaded), wait 15 seconds and try again, maybe you can do it 3 or 5 times. if it doesn't work, we should have the option to choose another AI model to handle this data. really simple things, but they make a huge difference to avoid errors in production flows. and that's just for llm nodes... error handling should be a feature anytime soon ### 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 18:18:33 -05:00
yindo closed this issue 2026-02-21 18:18:33 -05:00
yindo commented 2026-02-21 18:18:33 -05:00
Author
Owner
Copy Link
Copy Source

@acauaferreira commented on GitHub (Dec 9, 2024):

yes, very important!!

@acauaferreira commented on GitHub (Dec 9, 2024): yes, very important!!
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#7036
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?