Hi @Jason Bosco. My name is Guillermo, and I am @Scott Nei 's colleague at Method USA. Scott has taken some days off, and he'll return next week. Meanwhile, as you know, we moved to a new cluster with only one instance in our production environment, hoping to avoid the inconsistency issues Scott reported on March 27. Unfortunately, yesterday, we confirmed that we are experiencing the same behavior again: The issue we see is that documents seem to be "corrupted". Not all of them, but probably thousands. Among all of them, by coincidence or not, the same document (ID) is failing again on this new collection. You can check it using the same cURL commands:

curl --location '<https://hostname.a1.typesense.net/collections/products_prod/documents/search?q=&per_page=32&page=1&query_by=barcodes%2Cskus%2Cmanufacturer.mfrNumbers%2Cdescription%2CsupplierDescriptions&filter_by=productId%3A%3D319083%20%26%26%20catalogIds%3A%3D37480>' \

curl --location '<https://hostname.a1.typesense.net/collections/products_prod/documents/search?q=&per_page=32&page=1&query_by=barcodes%2Cskus%2Cmanufacturer.mfrNumbers%2Cdescription%2CsupplierDescriptions&filter_by=productId%3A%3D319083>' \

I am pointing this out to you just because if you were thinking the problem was limited to multi-instance clusters (only affecting the followers), it is not, making it harder for us to mitigate in our Production environment (even our current daily full-sync is not fixing this situation). We are thinking of creating new collections and loading all the documents. Unfortunately, this is the only way we have found to solve this. So, we would like to know: 1) Is it worth keeping these "corrupted" collections to let you investigate this issue? If we do this, we'll consume more RAM in our Production server, and we do not want to do this unnecessarily. 2) Could you share this situation internally so as to confirm you will be finding and fixing the root cause of this? we are extremely concerned since we are experiencing these issues in our Prod env (we are not able to do a downgrade since we are using features included in v28), and they are affecting us seriously. Thanks for your help. Any suggestions will be welcome.