A birch-sap bottling line deletes a bad batch item from Cosmos DB, but a latest-version change feed consumer never receives that delete. Why?
Select an answer to reveal the explanation.
Short Explanation
Latest-version mode is a highlight reel of surviving documents—deletes never make the cut. For delete (or TTL) notifications, use all-versions-and-deletes or write a soft-delete property the app can see.
Full Explanation
In latest-version change feed mode, Cosmos surfaces the current versions of items from inserts and updates; deletes and TTL removals are not included. Capturing deletes and intermediate versions requires all-versions-and-deletes mode (with its prerequisites) or an application-level soft-delete property. Consistency level and Event Hubs linkage are not what enables delete visibility in latest-version mode.