I've noticed already on several occasions that triggers get randomly deactivated. So far it seems to be only the file watcher triggers. I don't know if this has anything to do with this but all the file triggers are on network shares and not local drives.

The other odd thing that I noticed is that all the job's audit logs also get wiped out whenever the triggers got deactivated.

We also get this at times (not sure about the audit log)

There is always a reason and it should be stated in the log_serverDATE.txt. Please look in the log file.

Audit log is rotated so you might want to increase the days or number of rows you store in the Server settings.

---

I see the reason and I need a workaround. I'm watching a folder on a network share. The computer where this folder is located was shut down for maintenance at around 2:40 AM. The log file indicates that VC tried to reconnect for about 8 minutes (60 attempts) at which point it disabled the trigger.

How do I make it not deactivate the trigger in such cases?
How do I make VC send me an email whenever any trigger is deactivated or even better, when a trigger is auto-deactivated?

Thank you

You need to create another job which triggers on a de-activation of a trigger. Happy to email you our job if you'd like

OK!

I changed the retries on the file watcher to 300 and interval to 60 seconds. This will give me a retry window of up to 5 hours.
In addition I set up a job that sends an email whenever a trigger has been disabled or expired due to an error.

The last item that I would still like to resolve is the fact that Audit Log and Versions for the jobs are empty. How do I make them retain info for a year?

Thank you

Found it.

It's under Settings --> Log Settings --> Database Settings.
I unchecked the "delete after 14 days" option and kept the max of 2000 lines. That should do the trick for me.

😁

Something is still off.
On the file trigger I had changed the reconnect attempts to 300 and the interval to 60 seconds. When I looked at the logs I noticed two things. There was more than one entry for a given time stamp (4:11:07 AM) indicating the retry count and just a minute and 22 seconds later (4:12:29 AM) the number of retries jumped from 124 to 138. So clearly it's not waiting a minute between retries. See the log entries below.


4:11:07 AM Err Error watching directory (123/300), trigger: Wait for NHA Meditech DR file, folder: \\vhsmedidrsql01\f$\Export\NHA, filter: *.*, err: The directory name \\vhsmedidrsql01\f$\Export\NHA is invalid.
4:11:07 AM Err Reconnect->Error watching directory 'Wait for NHA Meditech DR file''. Directory: \\vhsmedidrsql01\f$\Export\NHA, filter: *.* that belonged to Job 'DR NHA Exports', retry 124\300, waiting: 60, err: The path is not of a legal form.
4:11:07 AM Err Reconnect->Error watching directory 'Wait for NHA Meditech DR file''. Directory: \\vhsmedidrsql01\f$\Export\NHA, filter: *.* that belonged to Job 'DR NHA Exports', retry 124\300, waiting: 60, err: The path is not of a legal form.
4:11:07 AM Err Reconnect->Error watching directory 'Wait for NHA Meditech DR file''. Directory: \\vhsmedidrsql01\f$\Export\NHA, filter: *.* that belonged to Job 'DR NHA Exports', retry 124\300, waiting: 60, err: The path is not of a legal form.
4:11:07 AM Err Reconnect->Error watching directory 'Wait for NHA Meditech DR file''. Directory: \\vhsmedidrsql01\f$\Export\NHA, filter: *.* that belonged to Job 'DR NHA Exports', retry 124\300, waiting: 60, err: The path is not of a legal form.
4:11:07 AM Err Reconnect->Error watching directory 'Wait for NHA Meditech DR file''. Directory: \\vhsmedidrsql01\f$\Export\NHA, filter: *.* that belonged to Job 'DR NHA Exports', retry 124\300, waiting: 60, err: The path is not of a legal form.
4:11:07 AM Err Reconnect->Error watching directory 'Wait for NHA Meditech DR file''. Directory: \\vhsmedidrsql01\f$\Export\NHA, filter: *.* that belonged to Job 'DR NHA Exports', retry 124\300, waiting: 60, err: The path is not of a legal form.
4:11:07 AM Err Reconnect->Error watching directory 'Wait for NHA Meditech DR file''. Directory: \\vhsmedidrsql01\f$\Export\NHA, filter: *.* that belonged to Job 'DR NHA Exports', retry 124\300, waiting: 60, err: The path is not of a legal form.
4:11:07 AM Err Reconnect->Error watching directory 'Wait for NHA Meditech DR file''. Directory: \\vhsmedidrsql01\f$\Export\NHA, filter: *.* that belonged to Job 'DR NHA Exports', retry 124\300, waiting: 60, err: The path is not of a legal form.
4:11:07 AM Err Reconnect->Error watching directory 'Wait for NHA Meditech DR file''. Directory: \\vhsmedidrsql01\f$\Export\NHA, filter: *.* that belonged to Job 'DR NHA Exports', retry 124\300, waiting: 60, err: The path is not of a legal form.
4:11:07 AM Err Reconnect->Error watching directory 'Wait for NHA Meditech DR file''. Directory: \\vhsmedidrsql01\f$\Export\NHA, filter: *.* that belonged to Job 'DR NHA Exports', retry 124\300, waiting: 60, err: The path is not of a legal form.
4:11:07 AM Err Reconnect->Error watching directory 'Wait for NHA Meditech DR file''. Directory: \\vhsmedidrsql01\f$\Export\NHA, filter: *.* that belonged to Job 'DR NHA Exports', retry 124\300, waiting: 60, err: The path is not of a legal form.
4:11:07 AM Err Reconnect->Error watching directory 'Wait for NHA Meditech DR file''. Directory: \\vhsmedidrsql01\f$\Export\NHA, filter: *.* that belonged to Job 'DR NHA Exports', retry 124\300, waiting: 60, err: The path is not of a legal form.
4:11:08 AM Err Reconnect->Error watching directory 'Wait for NHA Meditech DR file''. Directory: \\vhsmedidrsql01\f$\Export\NHA, filter: *.* that belonged to Job 'DR NHA Exports', retry 124\300, waiting: 60, err: The path is not of a legal form.
4:12:29 AM Err Reconnect->Error watching directory 'Wait for NHA Meditech DR file''. Directory: \\vhsmedidrsql01\f$\Export\NHA, filter: *.* that belonged to Job 'DR NHA Exports', retry 138\300, waiting: 60, err: The path is not of a legal form.

This is something that i've struggled with and because of it i've had to all but stop using file triggers. Most of them would be on a remote file share (local network... just a different server and/or appliance) and during maintenance it would potentially stop checking and then surprise, you miss a date. I am sure there is a reason for giving up eventually. But it would be nice to have a checkbox for a file watcher trigger that does the equivelant of "NEVER DISABLE" by any automatic means. Unless a human presses a button saying to disable it (as would be the case with any of our triggers, really) I never want it to give up. (Rick Roll anyone? haha).

Brian

Yeah agreed, I guess you need some kind of limit to stop file watches from killing a server (e.g. poll every 1 second) but in our case we do seem to get some random trigger disabling and would rather triggers just keep enabled forever.