langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Knowledge base retrieval test reported an error. #12279

New Issue
Closed
opened 2026-02-21 19:06:43 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:06:43 -05:00
Owner
Copy Link
Copy Source

Originally created by @singerTang on GitHub (Mar 28, 2025).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.0.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

retrieval test other knowlage base is ok

✔️ Expected Behavior

Image

❌ Actual Behavior

Error during query:[(locations’:[{’column’:6,li
'message':Cannot query field
"Vectorindexe0361f5d_3e78_40c1_903b_78c83
on type"GetobjectsObj".Did you mean
"Vector_indexfab989e4_c3ed_4e32_9547_98c88
'path':None}];Error during query:[(locations"line':1}].'message'：'Cannot query field
"Vector_index_e0361f5d_3e78_40c1_903b_78c83
on type"Getobjectsobj".Did you mean
"Vector_index_fab989e4_c3ed_4e32_9547_98c88
'path':None}]

Originally created by @singerTang on GitHub (Mar 28, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.0.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce retrieval test other knowlage base is ok ### ✔️ Expected Behavior ![Image](https://github.com/user-attachments/assets/c65065e9-d6d8-4d64-a0b1-4055a4182f8d) ### ❌ Actual Behavior Error during query:[(locations’:[{’column’:6,li 'message':Cannot query field "Vectorindexe0361f5d_3e78_40c1_903b_78c83 on type"GetobjectsObj".Did you mean "Vector_indexfab989e4_c3ed_4e32_9547_98c88 'path':None}];Error during query:[(locations"line':1}].'message'：'Cannot query field "Vector_index_e0361f5d_3e78_40c1_903b_78c83 on type"Getobjectsobj".Did you mean "Vector_index_fab989e4_c3ed_4e32_9547_98c88 'path':None}]
yindo added the 👻 feat:rag label 2026-02-21 19:06:43 -05:00
yindo closed this issue 2026-02-21 19:06:43 -05:00
yindo commented 2026-02-21 19:06:43 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 28, 2025):

I found a similar unsolved discussion titled "Why cannot find required text from knowledge base in Dify?" [1].

Regarding the error you're encountering, it seems related to querying fields in the vector index. This type of error can occur if there is a mismatch or incorrect configuration in the vector index setup. Here are some steps you can take to troubleshoot and resolve the issue:

  1. Check Vector Index Configuration: Ensure that the vector index is correctly configured and matches the expected field names. The error message suggests a mismatch in field names, so verify that the field names in your query match those defined in your vector index.

  2. Rebuild Vector Index: If you've recently changed the embedding model or made significant changes to the dataset, you may need to rebuild the vector index to ensure it aligns with the current configuration [2].

  3. Verify Embedding Model Consistency: Ensure that all documents in your dataset use the same embedding model to avoid vector dimension mismatches [3].

  4. Check for Typographical Errors: Double-check your query for any typographical errors in field names or syntax that might be causing the issue.

If these steps do not resolve the problem, consider reviewing the configuration and setup of your self-hosted instance to ensure everything is correctly aligned with the Dify version you are using.

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

@dosubot[bot] commented on GitHub (Mar 28, 2025): <!-- Answer --> I found a similar unsolved discussion titled "Why cannot find required text from knowledge base in Dify?" <sup>[[1]](https://github.com/langgenius/dify/discussions/10459)</sup>. Regarding the error you're encountering, it seems related to querying fields in the vector index. This type of error can occur if there is a mismatch or incorrect configuration in the vector index setup. Here are some steps you can take to troubleshoot and resolve the issue: 1. **Check Vector Index Configuration**: Ensure that the vector index is correctly configured and matches the expected field names. The error message suggests a mismatch in field names, so verify that the field names in your query match those defined in your vector index. 2. **Rebuild Vector Index**: If you've recently changed the embedding model or made significant changes to the dataset, you may need to rebuild the vector index to ensure it aligns with the current configuration <sup>[[2]](https://github.com/langgenius/dify/issues/16586)</sup>. 3. **Verify Embedding Model Consistency**: Ensure that all documents in your dataset use the same embedding model to avoid vector dimension mismatches <sup>[[3]](https://github.com/langgenius/dify/issues/16280)</sup>. 4. **Check for Typographical Errors**: Double-check your query for any typographical errors in field names or syntax that might be causing the issue. If these steps do not resolve the problem, consider reviewing the configuration and setup of your self-hosted instance to ensure everything is correctly aligned with the Dify version you are using. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/16481e36-d985-4168-ac92-37815bf60979?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/16481e36-d985-4168-ac92-37815bf60979?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/16481e36-d985-4168-ac92-37815bf60979?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/16481e36-d985-4168-ac92-37815bf60979?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/16481e36-d985-4168-ac92-37815bf60979?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/16481e36-d985-4168-ac92-37815bf60979?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/16481e36-d985-4168-ac92-37815bf60979?feedback_type=other)</sup>
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 👻 feat:rag
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#12279
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?