OK - thanks Wan.
I have literally tested exactly that scenario on a small scale and did not see the loss of update information, so I’ll need to repeat that and confirm. I stopped the stream reader, did an update, a delete and a recreate of the same object with different data and then started the stream reader and caught up on records - I was able to see all of the interactions and the accurate state of the object at each step. I saw this note in the documentation before and was concerned by it, so I tested it and didn’t see it exhibit itself.
I’ll re-run my tests to understand it better, but either way it shouldn’t be a blocker for us since we don’t do deletes regularly as part of the workflow (other than manual dev operations).
Thanks Wan!