VisualCron Support,

We're running VisualCron 5.3.1 on this particular server. We have a job that uses a file trigger on a Samba share. It has the following settings:

Main Settings tab:
Active: checked
Run delay: greyed out, but checked
Polling interval, Check every: 300 seconds

File tab:
File mask: *.
File/Folder watch type: Created
Notify filters: File name
Include subfolders: unchecked
Use polling (Samba compatible): checked
Trigger when file has been released: checked
On error reconnect attempts: 288
On error reconnect interval (seconds): 300

Timeout tab:
Nothing checked

Expires tab:
Nothing checked

Every once in a while the trigger will automatically become unchecked on the job's "Triggers" tab. What causes this? Is it because we had 288 failed reconnect attempts in a row? With an interval of 300 seconds (5 minutes), this is a 24-hour period.

Thanks.

Please turn on Extended debugging and retrieve the log_serverDATE.txt from the date it gets unchecked. Then we can debug what happened. Please send that file to support@visualcron.com

---

Henrik,

I enabled extended debugging and have been waiting for this to happen again. It finally did over this past weekend. It became unchecked sometime between 6PM on 1/15 and 9AM on
1/19. I'm sifting through the VisualCron server logs at the moment. If I don't find anything, can I zip them up and send them to you?

Thanks.

Yes, please send them to support@visualcron.com

---

Email sent. One note: the server hosting the Samba share that this trigger is monitoring did experience some downtime over the weekend. The downtime was longer than 24 hours, which exceeds the amount of time that I've set the trigger to retry (288 attempts at 300 seconds per attempt). Is it expected behavior for the trigger to become unchecked if the retry attempts are exhausted? If so, I'll just have to increase the number of retries.

Thanks.

Yes, that is the expected the behavior. The reason is that we need control over it. Please increase the time/retries if needed.

---