Drop pending changes to removed peer?

On client “machineC”, syncthing thinks that “machineB” is missing changes from “removedX”.

How do I get machineC to… stop and drop these changes that can never be resolved?

It seems like maybe there’s a check missing somewhere, or maybe this is very intentional because of the way peers may be visible only in a certain order and not all visible to each other?

Anyway, is there an easy to fix this that doesn’t require effectively removing it and re-adding the folder on all affected machines?

Er, actually it’s more obvious bug - removedX is actually still in the network, visible to everyone, but the dir in question is no longer synced to it from any device. So it should know to drop these changes presumably.

Just removing the dir from machineC and re-adding it was sufficient.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.