I hope that the agent nodes in the chatflow can have exception branches.

[xiaotang-12-ops]

Self Checks

• [x] I have read the Contributing Guide and Language Policy.
• [x] I have searched for existing issues search for existing 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.

I hope that the agent nodes in the chatflow can have exception branches.

2. Additional context or comments

No response

3. Can you help us with this feature?

• [ ] I am interested in contributing to this feature.

[crazywoola]

Why? And what operations will you do after the failure?

[chinuhou]

I agree, then we can show an error message to the user and tell him to try again in a few minutes, or do something else

[xiaotang-12-ops]

为什么？故障后你会做什么作？

为什么？故障后你会做什么作？

First of all, the current ChatFlow's agent is the most comfortable one for me to use because it combines the stability of workflows with the flexibility of agents, so I really like it. Adding exception branches would further enhance its stability.

Traditional agents are highly dependent on the large language model's (LLM) own capabilities. If ChatFlow's agent had an exception handling mechanism, we could at least choose to output fixed content when encountering LLM call failures. As for why I don't use the built-in LLM in ChatFlow, it's because this node cannot flexibly call the knowledge base. Alternatively, I need to add an additional LLM for intent recognition before the knowledge base node, which significantly affects my efficiency.

Therefore, I sincerely hope that ChatFlow's agent can add exception nodes, and I also hope that vision capabilities can be integrated.

[dosubot[bot]]

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

Issue Summary:

• You requested adding exception branches to ChatFlow's agent nodes to handle errors more gracefully.
• The discussion highlighted benefits like displaying error messages and retry options on LLM call failures.
• You noted the current agent's flexibility and stability but pointed out limitations with built-in LLM calls.
• You also expressed hope for future integration of vision capabilities to enhance functionality.
• The issue remains unresolved with no recent updates.

Next Steps:

• Please let me know if this issue is still relevant to the latest version of Dify by commenting here.
• If I don’t hear back within 15 days, this issue will be automatically closed.

Thank you for your understanding and contribution!