langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

Voyageai reanker [rerank-lite-2] raise "plugins invoke error" #87

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

Originally created by @gdmrw on GitHub (Mar 17, 2025).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • 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.

Dify version

1.0.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Create a knowledge base and add any file, embedding model choose voyage-3-lite, retrieval setting select hybrid search, choose rerank model as [rerank-lite-2], go to retrieval test type anything, and click test.

✔️ Expected Behavior

No response

❌ Actual Behavior

Image
Originally created by @gdmrw on GitHub (Mar 17, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [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. ### Dify version 1.0.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Create a knowledge base and add any file, embedding model choose voyage-3-lite, retrieval setting select hybrid search, choose rerank model as [rerank-lite-2], go to retrieval test type anything, and click test. ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior <img width="396" alt="Image" src="https://github.com/user-attachments/assets/5e155a48-7b12-4d73-8441-44fc0cfa9380" />
yindo closed this issue 2026-02-16 10:18:01 -05:00
yindo commented 2026-02-16 10:18:02 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 17, 2025):

Hey @gdmrw! 👋 I'm here to help you with any bugs, questions, or contributions while you wait for a human maintainer. Let's tackle this issue together!

A similar issue was previously reported and resolved. The issue titled "weight rerank not working properly in knowledge retrieval" was closed with a pull request that fixed the problem [1].

The "PluginInvokeError" you're encountering can be triggered by various conditions during plugin invocation, such as InvokeBadRequestError, which occurs when there is a bad request [2]. In your case, the "400 Bad Request" error from the Voyage AI API at the '/v1/rerank' endpoint could be due to several typical scenarios, such as no file uploaded, too many files uploaded, or invalid metadata, among others [3].

To address this issue, you might want to verify the input parameters being sent to the '/v1/rerank' endpoint. Ensure that the required parameters such as model, credentials, query, and docs are correctly formatted and provided. Additionally, check for any optional parameters like score_threshold and top_n that might be affecting the request [4].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 17, 2025): <!-- Greeting --> Hey @gdmrw! 👋 I'm here to help you with any bugs, questions, or contributions while you wait for a human maintainer. Let's tackle this issue together! <!-- Answer --> A similar issue was previously reported and resolved. The issue titled "weight rerank not working properly in knowledge retrieval" was closed with a pull request that fixed the problem <sup>[[1]](https://github.com/langgenius/dify/issues/10930)</sup>. The "PluginInvokeError" you're encountering can be triggered by various conditions during plugin invocation, such as `InvokeBadRequestError`, which occurs when there is a bad request <sup>[[2]](https://github.com/langgenius/dify/issues/14708)</sup>. In your case, the "400 Bad Request" error from the Voyage AI API at the '/v1/rerank' endpoint could be due to several typical scenarios, such as no file uploaded, too many files uploaded, or invalid metadata, among others <sup>[[3]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/guides/knowledge-base/knowledge-and-documents-maintenance/maintain-dataset-via-api.md)</sup>. To address this issue, you might want to verify the input parameters being sent to the '/v1/rerank' endpoint. Ensure that the required parameters such as `model`, `credentials`, `query`, and `docs` are correctly formatted and provided. Additionally, check for any optional parameters like `score_threshold` and `top_n` that might be affecting the request <sup>[[4]](https://github.com/langgenius/dify-docs/blob/main/en/guides/model-configuration/interfaces.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/9f14b8ed-a9f6-48c8-97ca-5c3617781e6b?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/9f14b8ed-a9f6-48c8-97ca-5c3617781e6b?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/9f14b8ed-a9f6-48c8-97ca-5c3617781e6b?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/9f14b8ed-a9f6-48c8-97ca-5c3617781e6b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9f14b8ed-a9f6-48c8-97ca-5c3617781e6b?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/9f14b8ed-a9f6-48c8-97ca-5c3617781e6b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9f14b8ed-a9f6-48c8-97ca-5c3617781e6b?feedback_type=other)</sup>
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label
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-official-plugins#87
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?