Knowledge base recall testing is inconsistent with the use of returned data in the workflow

[rainsun007]

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.4.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

The knowledge base uses the economic mode, the data returned when doing the recall test is inconsistent with the data returned by calling the knowledge base in the workflow, and the parameters used are determined to be completely consistent. This leads to tests that pass, but don't work as expected when used.

✔️ Expected Behavior

Returns data consistent with the recall test

❌ Actual Behavior

The returned data is inconsistent

[Gevtolev]

Please check if metadata filtering is enabled in the knowledge retrieve of the workflow. The recall test does not use metadata filtering.

[rainsun007]

I have only one knowledge base, and within this knowledge base, there is only one document.

[Gevtolev]

Can you provide a screenshot of the recall inconsistency? Thank you.

[dosubot[bot]]

Hi, @rainsun007. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

• You reported that in Dify v1.4.1 (self-hosted via Docker), the knowledge base recall test returns inconsistent data compared to actual workflow calls despite using identical parameters.
• The recall test passes, but the feature fails in practice.
• A maintainer suggested checking if metadata filtering is enabled in your workflow, as the recall test does not apply metadata filtering.
• You confirmed having only one knowledge base with a single document.
• The maintainer requested a screenshot to better understand the recall inconsistency, but no further updates have been provided.

Next Steps:

• Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open.
• Otherwise, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!