KB retrieval error management #18716

Closed
opened 2026-02-21 19:51:03 -05:00 by yindo · 0 comments
Owner

Originally created by @DavideDelbianco on GitHub (Oct 1, 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.

Since yesterday if I use rerank model by Jina AI the retrieval fails.
It is probably an issue on their side.

The knowledge retrieval node swallows the error and simply returns an empty response as if everything was fine but no documents were found.

A chatbot that relies on RAG cannot afford to stop working without any alarm because the node hides errors under the rug.

Just like LLM node raises exceptions and has retry and raises errors in case the remote API has issues, so MUST be the KB node that is using LLM models under hood

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 @DavideDelbianco on GitHub (Oct 1, 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. Since yesterday if I use rerank model by Jina AI the retrieval fails. It is probably an issue on their side. The knowledge retrieval node swallows the error and simply returns an empty response as if everything was fine but no documents were found. A chatbot that relies on RAG cannot afford to stop working without any alarm because the node hides errors under the rug. Just like LLM node raises exceptions and has retry and raises errors in case the remote API has issues, so MUST be the KB node that is using LLM models under hood ### 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 🐞 bug label 2026-02-21 19:51:03 -05:00
yindo closed this issue 2026-02-21 19:51:03 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#18716