400 Bad request: none query parameters

[Beckjiang]

Self Checks

• [x] This is only for bug report, if you would like to ask a question, please head to Discussions.
• [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 (我已阅读并同意 Language Policy).
• [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• [x] Please do not modify this template :) and fill in all the required fields.

Dify version

1.1.1

Cloud or Self Hosted

Cloud

Steps to reproduce

dataset’s hit-testing gets the response:

{
    "code": "invalid_param",
    "message": "Unexpected Response: 400 (Bad Request)\nRaw response content:\nb'{\"time\":4.1e-8,\"status\":{\"error\":\"Bad request: none query parameters\"}}'",
    "status": 400
}

POST https://cloud.dify.ai/console/api/datasets/XXXXXXX/hit-testing Request params:

{"query":"如何使用","retrieval_model":{"search_method":"hybrid_search","reranking_enable":false,"reranking_mode":"weighted_score","reranking_model":{"reranking_provider_name":"","reranking_model_name":""},"weights":{"keyword_setting":{"keyword_weight":0.3},"vector_setting":{"vector_weight":0.7,"embedding_model_name":"text-embedding-3-small","embedding_provider_name":"langgenius/openai/openai"}},"top_k":3,"score_threshold_enabled":false,"score_threshold":0}}

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

[dosubot[bot]]

Hello @Beckjiang! 👋 I'm here to help you with bug fixes, answer questions, and even assist you in becoming a contributor.

The "400 Bad Request" error with the message "none query parameters" typically occurs when the query parameter is missing from your request. However, in your case, it seems like the query parameter is present.

One potential issue could be the format or encoding of the request. Ensure that the JSON payload is correctly formatted and that the query parameter is properly included. Additionally, verify that the query string does not exceed 250 characters, as this is a validation rule in the API ^[1].

If the issue persists, double-check the request headers and ensure that the content type is set to application/json. This can sometimes cause issues if not correctly specified.

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}

[Beckjiang]

I'm really anxious; my application has completely lost the ability to answer questions by integrating the knowledge base. What's going on? Is it the cloud platform being used? @dosu

[acauaferreira]

ME TOO, really anxious, i am paying cloud pro, v1.1.1 ,lot and lot and lot of bugs, i am from 15 days just trying to solve dify bugs

[dosubot[bot]]

The issue you're experiencing might be related to the Dify cloud platform version 1.1.1, which has some known issues that could affect API request handling. These include configuration errors, provider configuration and quota issues, request and file handling errors, and limitations with certain functionalities like speech-to-text ^[1].

Given the "400 Bad Request" error you encountered earlier, ensure that your request is correctly formatted, especially the query parameter, which should not exceed 250 characters ^[2]. Also, make sure the request body is sent in the correct format, such as JSON, to avoid issues with special characters ^[3].

If these checks don't resolve the issue, it might be worth investigating any recent changes in your application or the Dify platform that could have impacted the integration with the knowledge base.

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}

[jqsl2012]

When will this error be fixed?

[crazywoola]

This is not a valid endpoint of our service API. POST https://cloud.dify.ai/console/api/datasets/XXXXXXX/hit-testing

It should be /datasets/{dataset_id}/retrieve without console.

[Beckjiang]

[crazywoola]

This is a bug related to our cloud db provider, we have reached out to them and they have fixed it already.