All V6 models compile a scan & compare table, scan each side and populate the table, make the (proposed) decisions, and (if deletions are involved) count how many deletions there will be and calculate that as a percentage. If the run is 'attended', and the Differences window is set to display, it will do so for your review. If you click Continue, and your max-deletions setting is (still) exceeded, you will be prompted about that (if 'unattended', the run is aborted)
These decisions (proposed actions) are then fixed. Nothing that happens in respect of the actual files affects them (except if a file cannot be copied because it has vanished, we can't copy it, obviously)
If files disappear after the scan stage (but were present up till then), the program absolutely will not delete the corresponding files on the other side (if it planned to copy them from Source, OTOH, it will actually log the disappearances - see below). This is because the decision was taken when you clicked Continue. Nothing changes those Decisions thereafter, unless it can't perform them. But it certainly doesn't delete them on Y because it can't copy them from X.
It's easy enough to test (I just did), with a dummy file on each side (same name but different date/time, to force it to copy Source over Dest). Wait till the Differences window appears, then - with the Differences window still open - go to the Source and deliberately delete that test file. Then click Continue in the Differences window. You'll get an error in the log saying
Failed to copy from Source : Cannot copy file (2): The system cannot find the file specified The file may have been deleted between the time it was scanned and the attempt to copy it was made
and the Destination copy will be still there...it absolutely will not delete the Dest copy (because the intended Action was to Copy To Dest, and nothing changes that)
Also, if files are deleted by the action of the program, it will log them as having done so.
Bear in mind if our products did what you are suggesting, we'd probably have closed by now.
These decisions (proposed actions) are then fixed. Nothing that happens in respect of the actual files affects them (except if a file cannot be copied because it has vanished, we can't copy it, obviously)
If files disappear after the scan stage (but were present up till then), the program absolutely will not delete the corresponding files on the other side (if it planned to copy them from Source, OTOH, it will actually log the disappearances - see below). This is because the decision was taken when you clicked Continue. Nothing changes those Decisions thereafter, unless it can't perform them. But it certainly doesn't delete them on Y because it can't copy them from X.
It's easy enough to test (I just did), with a dummy file on each side (same name but different date/time, to force it to copy Source over Dest). Wait till the Differences window appears, then - with the Differences window still open - go to the Source and deliberately delete that test file. Then click Continue in the Differences window. You'll get an error in the log saying
Failed to copy from Source : Cannot copy file (2): The system cannot find the file specified The file may have been deleted between the time it was scanned and the attempt to copy it was made
and the Destination copy will be still there...it absolutely will not delete the Dest copy (because the intended Action was to Copy To Dest, and nothing changes that)
Also, if files are deleted by the action of the program, it will log them as having done so.
Bear in mind if our products did what you are suggesting, we'd probably have closed by now.