7.0.6 - too many changes in file trigger, and Job running duplicate times - VisualCron - Forum

Community forum

TNT_CH
2014-07-30T08:33:29Z
Dear all

I have an issue with one job using file trigger. If more than 6 files are put at once in the folder the trigger gets deactivated (but not shown on the client, until I open and save the job). It shows the error:

A trigger was inactivated due to an error: Too many changes at once in directory: [folder]. The trigger was conntected to the job: [job name]

That's my file trigger:
Folder path: [UNC Path]
File mask: *.pdf
File/Folder watch type: Created
Notify filters: File name
Include subfolders = false
Use polling = false
Trigger when file has been released = true
On error reconnect attempts: 60
On error reconect interval: 10
Duplicate filedelay: 300

I tried to use the VisualCron network drives as well, but this didn't change anything.

While doing tests, I recognized that the job was running several times (up to five) for one file.

I have recreated the job from scratch and restarted the computer. That solved the multiple running until I had the first time again more than 6 files at the same time in the folder and reactived the trigger. Since then it agains run the job twice at the same time. It seems that only restarting VisualCron service stops this double trigger running.

Unfortunately I can't get rid of the "too many changes in file trigger"-error. No matter what I do.

I have a different job that has the same trigger, but to a different location. There are several hundred files copied at once in this location, and that one is working fine. The two jobs are not running at the same time and I don't see a difference in the file trigger (except the different location)

Any ideas how to solve this?! We receive up to 30 files at once and the trigger should be able to handle this.

Thank you in advance

Susanna

Support
2014-07-30T15:41:05Z
6 files it not a problem and 100 files not. But maybe the sum of total file triggers that you use cause this as Windows has a limit.

The limit is a memory limit. This limit is affected by a range of factors but get more easily drained if:

1. you are watching sub folders
2. the sub folders contain many files
3. you are using other settings than Created+filename

I suggest you go through your file triggers. I am sure the 6 file trigger will work if you deactivate the other. Please test that.

If you have Jobs running multiple instances at the same time maybe you have forget to set "Put Job in queue" in the main settings.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
TNT_CH
2014-07-31T12:07:16Z
Hi Henrik

I have checked all of my file triggered jobs.

There are 16 Jobs, only one of them is watching subfolders (on the local drive). I can't change that, as it's triggered by files downloaded from an email, there are around 10 - 15 mails a day.

All of them have only the watch type "created" and the filter "file name" activated. All are not run if the job is already running. Some of them won't put the job to the queue - for these we know that there won't be more than one file at a time. They have polling deactivated and they wait to run until the file is released.

There is only one job where I know we have more than 200 files at once in the directory. This one is triggered in the morning. The job where we have this issue is triggered in the evening. We receive here up to 30 files at once. All other jobs are triggered during one day (we work 24 hours) and have between 1 and 10 files at once.

If I monitor the memory of the server there are always around 2700 MB available (2000 on standby and 700 free). Let me know if I should check something more specific for the memory limit you mentioned.

I don't have any control when the job with the trigger issue is running. I am not in the office when it's running and I can't influence the amount of documents that are saved on the directory at once - testing won't be possible. As soon as I have again files that were not processed, I can test it and let you know.

Thank you for any more help

Susanna
Support
2014-07-31T18:27:07Z
It is not about the RAM but a limit in Windows. Please try to restart the VisualCron service to see if you still have the problem.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
TNT_CH
2014-08-11T14:24:28Z
Henrik

Restarting the service doesn't help.

I have the file trigger activated, as I need to have the file name for further use. Is there another way to get the file name? I would change the job to have a time trigger.

Thanks for help

Susanna
Support
2014-08-13T20:50:13Z
Originally Posted by: TNT_CH 

Henrik

Restarting the service doesn't help.

I have the file trigger activated, as I need to have the file name for further use. Is there another way to get the file name? I would change the job to have a time trigger.

Thanks for help

Susanna



You could use the List files Task to list files at a specific time each day. Then you use the loop on the output of that Task to process each file at a time.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top