I agree with what Henrik said. There are options on the file trigger to increase the retries, etc.. However, even so, we've still ran into issues when there are conditions I can't account for, so what we've done is set up a job on VisualCron that does nothing more than send an e-mail to our team anytime a trigger is enabled/disabled.
Now, if you are always adding/removing triggers, this might be annoying, but for us, we have specific change windows and know when those e-mails are appropriate. If we get an e-mail saying a trigger was enabled/disabled outside of these times, we go investigate.
Job with a 'VisualCron' trigger instead of an Interval. The trigger is based on Trigger Deleted, Expired, or both. (See Screenshot).
Then, the job has one simple Task: E-mail Task
Subject: {COMPUTER(Name)} - {TRIGGER(Active|LastTrigger|VisualCron.Result.Message)}
Typical stuff for From/To/ReplyTo address
Then the Text/body of the message:
{TRIGGER(Active|LastTrigger|VisualCron.Result.Message)}
If this was not on purpose, Go investigate.
Server: {COMPUTER(Name)}
bbusse attached the following image(s):