Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


t2c_running
2020-06-11T13:13:36Z
Good afternoon,

We have a Job that have the next File trigger:
"File Trigger. Monitoring folder 'D:\VisualCron\Jobs', file mask '*.*' for events Created,Changed,Deleted,Renamed."

This job has only a task: write to the file
"D:\VisualCron\Jobs\IT\Files 2 SQL\Files\{DATEFORMAT(yyyy.MM.dd.HH.mm)}.sql" 

the next line:
INSERT INTO data (path, filename, timestamp, changetype, path_old, filename_old) VALUES  ( "{STRING(Replace|{TRIGGER(Active|LastTrigger|File.Result.TriggerFolder)}|\|\\)}",  "{TRIGGER(Active|LastTrigger|File.Result.Name)}", "{DATEFORMAT(yyyy-MM-dd H:mm:ss)}", "{TRIGGER(Active|LastTrigger|File.Result.ChangeType)}", "{STRING(Replace|{TRIGGER(Active|LastTrigger|File.Result.OldFullPath)}|\|\\)}",  "{TRIGGER(Active|LastTrigger|File.Result.OldName)}" );


This job stop working next day while new files has created. We "solve" the problem checking "Reset trigger dependency state when saving Job", until it stops again (at next day more or less).

We have another job like this but File trigger is
"File Trigger. Monitoring folder 'D:\VisualCron\Jobs', file mask '*.zip' for events Created." and perform more complex tasks than the first and we don't have any issue with it.

Could you help us?

Thanks.

VisualCron Server 9.1.5 on Windows 2016

Edit: we have "Files 2 SQL" in "Exclude folder mask".
Sponsor
Forum information
Joey S
2020-06-24T18:14:05Z
I have this issue every once in a while, more so with certain servers than others. Typically, what I see happening is the server that you are monitoring for the files is unavailable beyond your timeout period you have set for the trigger OR the folder where the files will be is renamed.

To resolve I would suggest turning off the timeout for the trigger

The option is under the File tab - then next to the "On error reconnect attempts" there is a "No Limit" check box
t2c_running
2020-06-25T07:18:16Z
Originally Posted by: Joey S 

I have this issue every once in a while, more so with certain servers than others. Typically, what I see happening is the server that you are monitoring for the files is unavailable beyond your timeout period you have set for the trigger OR the folder where the files will be is renamed.

To resolve I would suggest turning off the timeout for the trigger

The option is under the File tab - then next to the "On error reconnect attempts" there is a "No Limit" check box



Hello Joey,

I applied the option you mentioned. We hope it solves the problem.

Thanks.
Scroll to Top