1 of 1 people found this helpful
1) File d is not transfered
2) File d is not deleted
1. It depends on the "max. waiting time" set in Advanced-> File watcher
Take into account that any file watched must meet the minimun iterations while the file is static. If filed.txt is added close to the max waiting time... it could ended as not ok as a result of "file size is not static".
2. Yes. It will not delete a file that has not been transferred.
In AFT and AFT operations on files are performed sequentially.
e.g. filea.txt will be transferred than it will be deleted -> fileb.txt will be transferred than it will be deleted ...
After completing the filec.txt it job will check if more files matching pattern are available at source -> if yes as per your query filed.txt that will be transfer and will be deleted.
Note: If data is being written in filed.txt then half file will be transferred (as file transfer is only a copy command, it requires only read access) but will not be deleted as for deletion the process which is writing the data in it should release it first.