Your 'transaction' does not include the expected acknowledgement
226 Transfer Complete
to signal successful receipt at the end of the transmission (this seems to be something that does happen on some FTP servers* with only larger files, but no idea why). An automated process like SB relies on that acknowledgement. But it should Resume on re-connection, unless your FTP server does not support the Resume function, or you have disabled Safe Copy in SBFree, which it sounds like you may have done. Our implementation of Resume relies on SafeCopy process to ensure we do not try to Resume on a live file which may potentially have changed in the meantime (whereas the copy under a temp name in SafeCopy is highly unlikely to have been modified by any other process)
* in theory it could also happen if a firewall or router switches off the command channel (because 'not used' for a while c/o the size of the file / longer transmission time). Hence the acknowledgement is sent, but never received.
226 Transfer Complete
to signal successful receipt at the end of the transmission (this seems to be something that does happen on some FTP servers* with only larger files, but no idea why). An automated process like SB relies on that acknowledgement. But it should Resume on re-connection, unless your FTP server does not support the Resume function, or you have disabled Safe Copy in SBFree, which it sounds like you may have done. Our implementation of Resume relies on SafeCopy process to ensure we do not try to Resume on a live file which may potentially have changed in the meantime (whereas the copy under a temp name in SafeCopy is highly unlikely to have been modified by any other process)
* in theory it could also happen if a firewall or router switches off the command channel (because 'not used' for a while c/o the size of the file / longer transmission time). Hence the acknowledgement is sent, but never received.