It would be a very convenient feature and simplify flows if we could specify a "growtime" on input file actions. Preferably on a per task basis; defaulting to 0 seconds.
So a setting that would specify the minimum (number of) seconds a file (in a folder on disk) has to be stable/not growing anymore before it's picked-up/processed by a Smart Mover task.
Such a grow-time would prevent Smart Mover from accidentally picking up files before they are complete, which incidentally, yet quite frequently in high volume processes, results in corrupt .jpg or .xml files.
Regular Windows/Linux file-locks seldom apply in situations where data is received through FTP and shared using mounted volumes etc.
To mitigate file corruption such problems we now fall back to adding "Run Command Line" tasks, and use e.g. a Linux find with applicable switches and actions to copy or move files. This works flawlessly, but greatly reduces the legibility and adjustability of the flows.
Please sign in to leave a comment.