@Stevek Re
See my comments on your other thread here:
That is by design on the first run of the replication system: after 3 or 4 replication events (from memory here I’m afraid) a share is then created by promoting the oldest of 3 snapshots kept at each end (send/receive) of the replication process.
Creating the same-name share at the receiving end will break replication. It does this automatically: it is, after-all replicating the chosen share: just confusingly over more than one replication event! So eventually the target share is auto-created. That may have been the cause of the problem you reported in the linked share where you reported: 'Failed to promote the oldest Snapshot to Share.
Lets continue in that thread as this one is from 2016!