Seeing an issues using CatchupSubscription where duplicate events are being written to the target (a clean Event Store)
When the CatchupSubscription indicates it has caught up, we re-run the CatchupSubscription using the same ES connection object and all the events are written again to our new Event Store (no idempotent writes)
If we conduct the same test, but create a new connection, we get idempotent writes.
Can anyone shed any light on why this would happen?
Expected version is always .Any and we always catchup the same stream.
EventStore version 4.0.1 and using core.net client api.