# Error Encountered in Weaviate Vector Search

**URL:** <https://forum.weaviate.io/t/error-encountered-in-weaviate-vector-search/1815>\
**Category:** Support\
**Tags:** bug, python\
**Created:** [March 25, 2024, 4:40pm UTC](https://forum.weaviate.io/t/error-encountered-in-weaviate-vector-search/1815 "2024-03-25T16:40:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Iammsd07](https://avatars.discourse-cdn.com/v4/letter/i/5fc32e/32.png) [@Iammsd07](https://forum.weaviate.io/u/Iammsd07)\
**Post date:** [March 25, 2024, 4:40pm UTC](https://forum.weaviate.io/t/error-encountered-in-weaviate-vector-search/1815/1 "2024-03-25T16:40:25Z")

</div>

Hi Team,

### Description

I encountered an error while attempting vector search after restoring the index (backed up with the same Weaviate version) from the S3 backup. The error message indicates an issue with object vector search at index class\_name, suggesting cleanup is needed.

> {‘data’: {‘Get’: {‘class\_name’: None}}, ‘errors’: [{‘locations’: [{‘column’: 6, ‘line’: 1}], ‘message’: ‘explorer: get class: vector search: object vector search at index class\_name: shard class\_name\_0g4KaFE5oZ4V: vector search: entrypoint was deleted in the object store, it has been flagged for cleanup and should be fixed in the next cleanup cycle’, ‘path’: [‘Get’, ‘Class\_name’]}]}

### Server Setup Information

- Weaviate Server Version: 1.22.0
- Deployment Method: Docker
- Number of Running Nodes: 1
- Client Language and Version: Python client (v3.25.3)

### Any additional Information

Search with where condition functions properly.  
Also want to mention that, after initially restoring the index, we proceeded to delete all data, reindex it, and then backed it up again. The error occurred following the restoration of this new backup in a new deployment.

Your help is much appreciated.

Thanks

---

<div class="post-metadata">

**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\
**Post date:** [March 25, 2024, 7:40pm UTC](https://forum.weaviate.io/t/error-encountered-in-weaviate-vector-search/1815/2 "2024-03-25T19:40:16Z")

</div>

Hi @Iammsd07 !

I believe this might be the same bug:

> <https://github.com/weaviate/weaviate/issues/4227>
>
> \### How to reproduce this bug?
> 
> delete all records from a tenant with a query l…ike 
> \`\`\`python
> {"match": {"class": weaviate\_class, "where": {"path": \["title"\], "operator": "NotEqual", "valueText": "\_\_kttGNcJ890\_"}}}
> \`\`\`
> where the valueText NotEqual to a dummy value has the aim of selecting all records
> 
> Then, immediately after the delete operation (done via REST call) successfully returns, we insert a batch of documents w/ vectors in the tenant (about 10 documents), via \`/v1/batch/objects\`.
> 
> Then immediately after, we start getting this error (please note it doesn't happen always) when querying in vector mode:
> 
> \`explorer: get class: vector search: object vector search at index xxxxxx: shard xxxxxxxx: vector search: entrypoint was deleted in the object store, it has been flagged for cleanup and should be fixed in the next cleanup cycle\`
> 
> Then after something like a minute, vector queries will start working again BUT they won't return all results, but only one single document. Ie: let's take a query with a limit of 4, which is expected to always return 4 documents, it will return only 1 document. BM25 queries on the contrary would return 4 documents, from the same tenant. Some other times we have also seen duplicate results from vector queries, instead of one single document.
> 
> \*PLEASE NOTE THIS BEHAVIOR DON'T OCCUR SYSTEMATICALLY, I mean that after the delete-insert procedure, sometimes everything goes smoothly and in this case subsequent vector searches will be always fine. On the contrary, when something goes wrong with delete-insert, vector searches will always present issues (be them duplicate documents, or only one document returned, etc.).
> 
> \### What is the expected behavior?
> 
> all records are deleted, new records are inserted, no errors are returned on immediate queries and vector queries work normally.
> 
> \### What is the actual behavior?
> 
> we get an error on querying after delete-insert, and when the error resolves, vector searches show a weird behavior.
> 
> \### Supporting information
> 
> \_No response\_
> 
> \### Server Version
> 
> 1.23.7 on your cloud servoce weaviate.cloud
> 
> \### Code of Conduct
> 
> \- \[X\] I have read and agree to the Weaviate's \[Contributor Guide\](https://weaviate.io/developers/contributor-guide) and \[Code of Conduct\](https://weaviate.io/service/code-of-conduct)

At least the error messages and object deletion is similar.

Can you relate your issue with this one?

Thanks!