Knowledge metadata search bug

[BUG?] Metadata Filter in Knowledge Search Node Not Working Since v1.13.0

In a workflow that was working correctly until about a week ago (around the v1.13.0 release), the metadata filter suddenly stopped working.

Environment

  • Dify Cloud

Current Status

  • Metadata product_name = "ProductA" is set in the knowledge base.
  • product_name = [Variable: user_input] is set in the metadata filter of the Knowledge Search Node.
  • Even when executed with user_input = "ProductA", { "result": [] } is returned.
  • The cencern value is not correctly passing the knowledge, and it’s possible that the search is not being performed using metadata.

Steps Taken

  • Confirmed field name match.
  • Even when changing the Variable to a Constant (fixed value \"ProductA\"), [] is returned.
  • Even when rolling back the workflow to last month’s version, it does not improve.

In v1.11.3, fix DatasetRetrieval._process_metadata_filter_func miss in operator (#30199) was fixed, but a regression may have occurred in a subsequent update.

Is anyone else experiencing a similar issue?

2 Likes

I am experiencing the same issue. Filtering metadata by variables does not work for me. Constant values work as expected.

1 Like

If the part in the attached photo is a variable, searching is not possible; if it’s a constant, searching works without issues. Until recently, I was able to search using variables, so if there’s a way to search for metadata using variables, please let me know.

1 Like

I am also struggling with the exact same symptoms. Was it working before?

This appears to be a bug and has already been reported on GitHub.
I plan to fix it as is, but it will likely be tomorrow or later, and perhaps the people inside (the project/company) might be faster.

It used to work. It feels like it suddenly stopped working with variables since March…

Thank you. I will wait for it to improve.

Thank you so much. I hope it can be fixed soon :flexed_biceps:

It seems like it was quickly addressed before I even started.
It will be fixed in the next release, so please wait for the release :relieved_face: