We recently saw a problem with one of our file-arrive trigger jobs where it ignores the task if the trigger folder has too many changes.

The trigger is:
Folder path:K:\MSSQLBackup
File mask: *full*.bak
Include sub-folders
Trigger when file has been released.
File/folder watch type=Created
Notify filter: file name



7/11/2011 1:56:42 AM Info Job started: Prod_DBA_Maint_DB2_003B_FileArrive_Zip_Full_to_K_MSSQLBackup_Zipped
7/11/2011 1:56:42 AM Info Task: ***JOB NOTES***(see SQL tab) (inactive) was skipped because it was inactive.
7/11/2011 1:56:42 AM Info Task started: Zip_Full_to_K_SQLBackup_Zipped (67844)
7/11/2011 1:56:42 AM Err Error watching directory, err: Too many changes at once in directory:K:\MSSQLBackup.
7/11/2011 1:56:42 AM Debug Reconnected file trigger. Directory: K:\MSSQLBackup, filter: *full*.bak

It missed one of the files completely that was critical to our production. We are using 5.7.4 on this server. Is this a bug?

Hi devonway,

No this is not a bug. A Windows buffer has restriction the number of events.
Microsoft: FileSystemWatcher 

If you search in the forum, I had previously posted this as well (version 4.xx), so please read this as well.
The trigger will be deactivated if this happens, so you have to watch out.

Regards,
Erik

---

I recommend using 1 File/Folder watch type and one Notification filter at a time. Also make sure that you do not watch a sub folder that contains _too_ many sub folder changes.

---