Hello,

I've ran into an issue a few times where a file is written to a folder but WatchDirectory has a delayed reaction to it. 
I current have a Run Multiple Sub Task setup

• Fast Method

• Events - FILENEW and FILECNHG

• Run as a Windows Service

I also have several other tasks setup in the same fashion, all other feeds reacted to the file when it was created.

How can I further dig into the system to figure out why delay?

Hi Gert,

I did eventually figure out what was happening.  I originally had debug information turned on for 1 sub-task but not the other 3, nor did I have FTP conversation enabled.  Well after I did turn on all of those options I analyzed the log and clearly saw that the issue was on the receiving server, and not ours or Watch Directories issue.

Basically the final task in my set is configured to move the file to a "processed" folder, the server it was connecting to would stall for 4-5 minutes before timing out which reset the WD task (connect and send file) which worked without timing out.  The side effect of waiting for the timeout meant the folder was accumulating more files to send but had to wait 4-5 minutes for the task to finish and kick off for the new file queued.  If another time-out period occurred, even more files got queued and delayed.

Ultimately I ended up created four separate tasks which monitored four directories, one for each end-point server.