*Contents linked from this page might be in Japanese.
■Causes
File trigger detects the new file creation/modification/deletion using the file system in which the targeted file exists.
Therefore, the targeted file system might detect the file in an incomplete status and might fire the file trigger if the specification is to detect the file existence before completing the new file creation/modification/deletion.
As an instance, if the file system detects the targeted file before completing the file copy, this kind of problem arises.
*The above mentioned case is described in the points to be noted available in the help menu of file trigger. Also refer to the URL mentioned in Reference Information.
■Counter Measures
Once the file operations (New creation/Move) of targeted process are completed, add the process to output the file for monitoring in an extremely small capacity and in the file trigger set the file in such a way that the file for monitoring is monitored.
The smaller the file capacity, shorter the time taken for new creation/update and thereby the problem occurrence can be suppressed.