Slow Response-Time For A Triggered Folder Rescan

[Darius1968]

This attached log file is about a successful - triggered by Windows notifying IMatch of folder modification - folder rescan.  However, it was delayed - from the time of notification - by over 2 min.  Are there any specific reasons for this? 

[Mario]

When IMatch receives messages from Windows about changes in a folder, it waits for a certain period after the last message was received (10 seconds or so, depending on what else is going on).
Some applications create temporary files while saving. And when the temporary file has been written successfully, they delete the original file and rename the temporary file. Or similar operations. it would be bad if IMatch would react immediately on the "delete file" before the original application had a change to rename the temporary file. You could lose data.

[Darius1968]

That makes sense.  However, does this logic also apply to the saving of a simple few-words text file? 

[Mario]

I cannot look into your system.
Most likely Windows did several messages, always re.-triggering the timeout and thus postponing.
Maybe your virus checker or a background process did something with the folder, causing locks or additional messages.
Maybe something strange is going on on your system, sucking up all the memory and causing all kinds of strange behaviors.