---
title: "Comment by Mihai_LeanZero on \"Deleting Personal Data from a RAG System in .NET\" | Hashnode"
description: "The verification section is the strongest part of this for me -- treating \"document not found\" as the only thing that establishes logical absence, rather than t"
url: "https://hashnode.com/posts/deleting-personal-data-from-a-rag-system-in-net/6abd5fa1c02e2338b2100943/comment/6abf507dc548f1f021941369"
---

[Discussion](https://hashnode.com/posts/deleting-personal-data-from-a-rag-system-in-net/6abd5fa1c02e2338b2100943)

Comment [Deleting Personal Data from a RAG System in .NET](https://hashnode.com/posts/deleting-personal-data-from-a-rag-system-in-net/6abd5fa1c02e2338b2100943)

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero)

[Oct 2](https://hashnode.com/posts/deleting-personal-data-from-a-rag-system-in-net/6abd5fa1c02e2338b2100943/comment/6abf507dc548f1f021941369)

The verification section is the strongest part of this for me -- treating "document not found" as the only thing that establishes logical absence, rather than trusting the delete call's own success response. One thing worth adding for Azure AI Search specifically: deletes propagate to replicas asynchronously, so a verification read issued right after the delete request can still land on a replica that hasn't caught up yet and come back with the document still present. If the verification step runs immediately after the delete call in the same task execution, that's a false "still there" -- harmless if it just triggers a retry, but it could get misread as "deletion failed, escalate" when the delete actually succeeded. Feels like it wants the same settle/retry treatment you already give the delete itself, applied to the verification read too.

[Patrick Kearns](https://hashnode.com/@fullstackcity)

[Oct 2](https://hashnode.com/posts/deleting-personal-data-from-a-rag-system-in-net/6abd5fa1c02e2338b2100943/comment/6abf507dc548f1f021941369#reply-6abf5239632f5c0e51e90138)

Yeah good point, the verification read needs its own bounded retry window. I'd treat "still present" immediately after deletion as pending verification, then retry with backoff before escalating. If it remains present beyond that window, the erasure request stays open for investigation.
