Trigger: Moody File Monitor

sanjay · Post by **sanjay** » Fri Oct 21, 2011 8:24 am

Can someone explain how file monitor trigger works. I have a script that is monitoring a set of folders (about 50 folders + sub folders on a network drive with a few thousand file in them in total) for changes (new files + changed files) and is then supposed to notify users the folder belongs to.
What I find is that when I run robotask as service, the file monitor event does not fire. I assumed it could be due to the large number of folders and files it is monitoring, so created another script to monitor just one folder and that would not fire either. I then ran robotask manually and the trigger monitoring single folder works, but the main trigger still would not fire. Is there a limit on how many files it can monitor?

Post by **Oleg** » Fri Oct 21, 2011 8:59 am

Probably File Monitor have problem with network folders in service mode.
Trigger can't access any network resources in service mode.
We'll investigate the problem and will try to fix it.

Is there a limit on how many files it can monitor?

There is no limit. But if you use very large folders it may slow down all work of the program.

sanjay · Post by **sanjay** » Mon Oct 31, 2011 10:49 am

Any updates on this?

Post by **Oleg** » Mon Oct 31, 2011 12:51 pm

Any updates on this?

Unfortunately no.

I recommend you to start RoboTask service under some user account. You can change this setting in service manager of Windows.
In this case all triggers of RoboTask can access network recources with user's rights.
Also I recommend to use UNC names, because there are no mapped network drives in service mode.
Read more about UNC names here.