I had previously setup a test where I created a stream, captured the resumeToken from the first event, shut down the stream, reconnected with the resumeToken. This worked to resume the stream from the last change event. But, this did not work when the primary was shutdown.

Yes, for node, the write concern has to be set but does default to w:1.

Thanks for pointing to the test code. I had not looked there before, but it does expect the application code to keep track of the resumeToken.

So, I can read the _id but I don’t know how to cache the resumeToken between change events. Had thought about using memcache but there is, no doubt, a simpler solution. Further work required!