What if last sync is not succesfull?
I have an automated proccess using windows schedulers running in 3 steps
1. Export files from Software
2. Transfer those files to a given FTP
3. Move those files to archive so that they don't sync again based on if the transfer scheduler is successful. This is done so that the files in the destination are moved to another folder which i don't have access and i really don't want to even think what will happen if i sync those files again.
Now all of the above works flowless except from one condition. Client internet connection is not good due to it's server location and sometimes disconnect before file transfer so files are moved to archive and will not sync again. I thought that using an XML on the archive scheduler to run only if the previous scheduler is sucessful was going to work but obviously scheduler does not know the result of winscp.
Is there any other work arround in an automated way? Even if it means changes in the stracture of this process
1. Export files from Software
2. Transfer those files to a given FTP
3. Move those files to archive so that they don't sync again based on if the transfer scheduler is successful. This is done so that the files in the destination are moved to another folder which i don't have access and i really don't want to even think what will happen if i sync those files again.
Now all of the above works flowless except from one condition. Client internet connection is not good due to it's server location and sometimes disconnect before file transfer so files are moved to archive and will not sync again. I thought that using an XML on the archive scheduler to run only if the previous scheduler is sucessful was going to work but obviously scheduler does not know the result of winscp.
Is there any other work arround in an automated way? Even if it means changes in the stracture of this process
