Problem with Knowledge Base Queries after Updating to Dify 1.2.0

[MitraSafarinejad]

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

After updating Dify to version 1.2, I'm encountering the following error when querying my existing knowledge bases:

Error during query: [{'locations': [{'column': 6, 'line': 1}], 'message': 'Cannot query field "Vector_index_b1df11d8_9f64_4c01_be16_60bc3b8d7d1f_Node" on type "GetObjectsObj".', 'path': None}]; I discovered that this issue can be resolved by changing the Embedding Model. However, I have a large number of documents already uploaded, and manually updating the embedding model for each document or knowledge base is not feasible.

✔️ Expected Behavior

Queries to existing knowledge bases should continue working normally after updating to version 1.2 without needing to manually change embedding models or reprocess documents.

❌ Actual Behavior

Queries to existing knowledge bases fail with the following error:

Error during query: [{'locations': [{'column': 6, 'line': 1}], 'message': 'Cannot query field "Vector_index_b1dfd8_9f64_4c01_be16_60bc8d7d1f_Node" on type "GetObjectsObj".', 'path': None}]; Error during query: [{'locations': [{'column': 6, 'line': 1}], 'message': 'Cannot query field "Vector_index_b1dfd8_9f64_4c01_be16_60bc8d7d1f_Node" on type "GetObjectsObj".', 'path': None}]

[dosubot[bot]]

I found two similar closed issues related to your problem:

1. Dify1.2 knowledge base cannot be retrieved - No solution found in the comments ^[1].
2. Embedding模型不生效 - No solution found in the comments ^[2].

Regarding your issue, the error "Cannot query field 'Vector_index_b1df11d8_9f64_4c01_be16_60bc3b8d7d1f_Node' on type 'GetObjectsObj'" can be resolved by waiting for the background re-indexing process to complete. Unfortunately, there is no visible indicator of progress, so patience is required. If the error persists, you may need to delete the dataset and upload it again, as the vector index needs to be rebuilt when switching between different embedding models ^[3].

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}

[crazywoola]

@JohnJyong Can you take a look at this?

[JohnJyong]

pls provide your local vdb and more log error info, thanks @MitraSafarinejad

[MitraSafarinejad]

Hi,

Currently, I do not see any specific additional log details related to this error — the only error message I get is the one I shared earlier.

Here is my configuration:

Embedding Model: text-embedding-3-small

Rerank Model: rerank-multilingual-v3.0

Top K: 3

Please let me know if there is any other specific log or file I should check or share to help troubleshoot this issue.

Thanks!

[MitraSafarinejad]

Hi @JohnJyong ,

I wanted to follow up regarding the bug I reported earlier. Do you have any updates on this issue? Thank you

[dosubot[bot]]

Hi, @MitraSafarinejad. 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 after updating to Dify 1.2.0 (self-hosted via Docker), queries to existing knowledge bases fail with a missing field error.
• Temporarily changing the embedding model fixes the issue, but reprocessing many documents is impractical.
• It was suggested the error might resolve after background re-indexing completes, or datasets might need re-uploading due to vector index rebuilding.
• Maintainer JohnJyong requested local database files and more logs for troubleshooting, but you have not observed additional error details yet.
• Another maintainer, crazywoola, has also tagged JohnJyong to investigate further.

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!