QWEN2.5-VL-72B return json with null property when it was used as text classify

[ensleep]

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

0.15.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

使用QWEN2.5-VL-72B作为问题分类器，返回的json是null，根据日志，返回结果为{}。

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

[dosubot[bot]]

The issue you're experiencing with the QWEN2.5-VL-72B model returning a JSON with null properties when used as a text classifier in Dify could be related to a few known issues:

1. Bug in Dify v0.15.3: There was a bug where the rerank model switch in 'Recall Settings' would automatically turn on, causing empty results even when disabled. This bug was fixed in a later update ^[1].

2. Incorrect JSON Structure: Ensure that the API response follows the required JSON structure. The response must include a 'records' array containing objects with 'metadata', 'score', 'title', and 'content' fields. If the response doesn't match this structure, it might result in null or empty JSON ^[1].

You might want to check if these issues apply to your setup and consider updating to a newer version if available.

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}

[ensleep]

@dosu not the same bug

[dosubot[bot]]

If the issue with the QWEN2.5-VL-72B model returning a JSON with null properties is not related to the known bug or incorrect JSON structure, consider checking the following:

1. Model Configuration: Ensure that the model is correctly configured in Dify. Verify that all necessary input parameters and settings are properly set up.

2. Logs and Debugging: Check the logs for any error messages or warnings that might provide more insight into why the JSON response is null. This can help identify if there are any configuration or runtime issues.

3. Data Input: Ensure that the input data being sent to the model is valid and correctly formatted. Invalid or unexpected input can sometimes lead to null responses.

4. Version Compatibility: Confirm that the version of the QWEN2.5-VL-72B model you are using is compatible with your current version of Dify. Incompatibilities can sometimes cause unexpected behavior.

If none of these steps resolve the issue, it might be helpful to look for any recent updates or patches for Dify or the model that address similar issues.

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}