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

Workflow adds global exception handling to unify return messages. #3218

New Issue
Closed
opened 2026-02-21 17:55:11 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:55:11 -05:00
Owner
Copy Link
Copy Source

Originally created by @check321 on GitHub (May 12, 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).
  • Pleas do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing?

When I use the workflow(v0.6.7) ,the JS node occasionally triggers exceptions (the reason is currently unknown, re-executing will return to normal), causing the workflow to directly return exception information.

2. Describe the feature you'd like to see

Therefore, I hope to add global exception handling capabilities to the workflow to uniformly return user-friendly information.

3. How will this feature improve your workflow or experience?

Unify exception handling in the workflow and customize the return of more friendly information.

4. Additional context or comments

No response

5. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @check321 on GitHub (May 12, 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] Pleas do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? When I use the workflow(v0.6.7) ,the JS node occasionally triggers exceptions (the reason is currently unknown, re-executing will return to normal), causing the workflow to directly return exception information. ### 2. Describe the feature you'd like to see Therefore, I hope to add global exception handling capabilities to the workflow to uniformly return user-friendly information. ### 3. How will this feature improve your workflow or experience? Unify exception handling in the workflow and customize the return of more friendly information. ### 4. Additional context or comments _No response_ ### 5. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the 🌊 feat:workflow label 2026-02-21 17:55:11 -05:00
yindo closed this issue 2026-02-21 17:55:11 -05:00
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 🌊 feat:workflow
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#3218
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?