I'd like that ancient local replica can't affect to the server replica and the server replicas hasn't a differences between each other.
I've had this problem a bad local replica affects a one server replica that it put a lot of old documents, but I've lucky because only server are affected and I made a program to check the difference between the server affect respect the other and I can find it.
In the picture I can recognise what's the bad document Created in 2015, modified 2019 and added this year.
I asked about it and there're no solution and they propose me that I give an idea.
The idea is, local replica with the user are reader, always one direction and the local server can force the local replica has the same documents,.
When the user is editor but can't delete documents, when is replica, the deletions from the server to local, and from local can add documents.
I'd like also a configuration that after several days the replica is always in one direction from the server to the local.
In brief the best solution is the user is reader only allow one direction replica else after several days that the local replica is not replicate only one direction from the server to the local .
It will be fantastic has a view that the user can see which documents are added, deleted in both direction and the possibility to do a restore.
Enable Purge Interval Replication Control (PIRC). This prevents unwanted replication of deleted documents.