@sebasb Yes the replication feature was a big fix in this stable channel run, and a sad breakage in our last testing run.
Remember we still have a fragility in the replication system re existing snapshots from prior failed replication tasks. It will indicate this as a failure if you are affected. Just delete the ‘blocking’ snapshot if you are affected by this and kick off another. Need to get to this one really. From memory the ‘blocking snapshot’, if it exists, is on the sending machine.
Hope your twin machines settle in again.