Fast Load trigger

The most common case I know of is the file is being actively created and before that completes, the import attempt starts. One strategy is to create the file (or, copy it from a remote node) into a different local directory first, then move it to the import directory. The "move" will be nearly instantaneous. 

Also you might try the "aahImport.exe" utility and see if that handles your scenario better than the automatic import from "C:\Historian\Data\DataImport\FastLoad"

The most common case I know of is the file is being actively created and before that completes, the import attempt starts. One strategy is to create the file (or, copy it from a remote node) into a different local directory first, then move it to the import directory. The "move" will be nearly instantaneous. 

Also you might try the "aahImport.exe" utility and see if that handles your scenario better than the automatic import from "C:\Historian\Data\DataImport\FastLoad"