On A, Syncthing doesn’t see the move, but it sees that the original file is gone, and an new file with the same hash is somewhere else.
But for some reason it seems that in your situation, the delete was synced before the “new” file, so B deleted the original file before wanting the “new” file.
BUT, How can I make delete was synced after the “new” file?
I have tried different MOVE, sub folder, parent folder, new folder…it always do “Del and New” in every time.
If it’s a lot of files, that’s going to happen, as we can’t send all the changes in a single message, and syncthing starts working on stuff as soon as it gets a single message, which means that deletes can happen before creates (which means we’d fail to recognize renames).
Best bet is to copy, wait to get in sync, and delete.
I just move only ONE large video file which is about 700MB from a folder to another. only one file.
Is it possible have some different code between windows version and linux version?
it’s really hard to know why.
Have you actually specified the folder ID?
The path should be relative path to the folder root.
If your folder is at c:\foo\bar, and file is at c:\foo\bar\baz\nuff\some.iso, then the path should be /baz/nuff/some.iso.
I’ve explained above how you compose a path, you are also missing folder= in the URL as explained in the docs. Anyways, moving it again might not reproduce the issue, hence you should do it on the old file name.
I am interested in both, the old file and the new file on the origin where the rename happened, when you are actually sure it had to be redownloaded.
It’s not clear if this new file had the same side effect.