Wan,
Thanks for responding. I hadn’t seen this kind of issue other than dev-initiated bulk deletes with robo3t, so it may be changing the object and then deleting it, but either way the scenario is a match for what I’m seeing. I saw the documentation and had assumed that this was not relevant since I had tested this case manually by issuing an insert, a delete, a recreation and an update and the oplog was returning accurate results each step along the way even though I didn’t call it until after all of the operations had been applied. Does this really only show up when the number of deletes is excessive?
At any rate, this is the scenario that I’m seeing since I know it was dev deletes - thanks for confirming since my simple tests early on showed that I could see through deletes for simple operations. Because of this, I wasn’t expecting this to still be an outstanding issue.
Thanks Wan!
Jeremy Buch