mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
PluginInvokeError #704
Reference in New Issue
Block a user
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?
Originally created by @luoMonkeyKing on GitHub (Oct 11, 2025).
Self Checks
Dify version
1.9.1
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
When I use the knowledge base to search, I get the following error
api logs:
✔️ Expected Behavior
The knowledge base is in normal use
❌ Actual Behavior
No response
@dosubot[bot] commented on GitHub (Oct 11, 2025):
The 400 Bad Request PluginInvokeError from the Siliconflow rerank API is likely caused by a mismatch or missing parameters in the request payload. Recent changes in Dify's knowledge base workflow updated how reranking configuration is handled, including renaming the
hybridSearchModeparameter toreranking_modeand adding stricter validation for reranking model and provider names when reranking is enabled. If your configuration is missing these fields or uses outdated parameter names, the Siliconflow API may reject the request with a 400 error.To resolve this, double-check that your knowledge base node configuration includes the correct
reranking_mode,reranking_model, and provider/model names as required by the latest Dify version. If possible, enable debug logging to inspect the outgoing payload and ensure it matches the Siliconflow API's expectations. If you are running an older version, consider updating to the latest release, as recent fixes address related issues with retrieval and reranking configuration (see PR langgenius/dify#26380, see PR langgenius/dify#25789).To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

@dosubot[bot] commented on GitHub (Oct 11, 2025):
The 400 Bad Request (PluginInvokeError) from the siliconflow.cn rerank API is likely caused by a malformed or incomplete request payload, often due to missing or misconfigured reranking model settings in your knowledge base configuration. Recent updates require that when reranking is enabled, you must specify both the reranking provider name and model name. If these fields are missing, the request sent to the siliconflow API will be invalid and trigger this error. Double-check your knowledge base node settings to ensure all required reranking fields are filled out, especially after recent changes that renamed configuration properties (e.g., from
hybridSearchModetoreranking_mode) and added stricter validation for reranking models. Misalignment between your configuration and these requirements is a common cause of this error.For more details, see the relevant code and configuration changes:
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
