The community members suggest that the issue described in the post is likely a mismatch between the qdrant-client version and the deployed instance of Qdrant. One community member notes that they had to update their Qdrant instance internally at some point, which may have caused the issue. However, there is no explicitly marked answer in the comments.
