I have a job that used to be setup to run, every 15 minutes between the times listed in two different time intervals
6am - 6 pm
6:30 pm - 9 pm

So at 6:00 am the job would run, then again at 6:15 am and 6:30 am etc until 6 pm then stop until 6:30 pm and start again every 15 min until 9pm. Essentially it would be skipped twice between 6 am and 9 pm.

I had a number of jobs like this and there were a few times we changed the 6 pm time to 6:20 pm and the 6:30 pm time to 6:50 pm. Then we changed it back for various reasons. So instead of having to change multiple jobs again. it made more sense to set these jobs up to run 6 am - 9pm with one time exception that can be changed easily instead of changing multiple triggers on multiple jobs

What happens now in v9.6.5 that did not happen in 9.4.5 is that I get a "Missed job" in the event log.


I do not want this because it is filling my whole log with things I want to happen. Is there a way that I can turn it off?

I have a job that used to be setup to run, every 15 minutes between the times listed in two different time intervals
6am - 6 pm
6:30 pm - 9 pm

So at 6:00 am the job would run, then again at 6:15 am and 6:30 am etc until 6 pm then stop until 6:30 pm and start again every 15 min until 9pm. Essentially it would be skipped twice between 6 am and 9 pm.

I had a number of jobs like this and there were a few times we changed the 6 pm time to 6:20 pm and the 6:30 pm time to 6:50 pm. Then we changed it back for various reasons. So instead of having to change multiple jobs again. it made more sense to set these jobs up to run 6 am - 9pm with one time exception that can be changed easily instead of changing multiple triggers on multiple jobs

What happens now in v9.6.5 that did not happen in 9.4.5 is that I get a "Missed job" in the event log.


I do not want this because it is filling my whole log with things I want to happen. Is there a way that I can turn it off?

Hi Joey,

You can go to Client settings -> Client events and then uncheck "Missed job".

---

I was hoping that would be a separate feature where the time exception would not count as a "miss". I did what you suggested. Thanks for the reply

I was hoping that would be a separate feature where the time exception would not count as a "miss". I did what you suggested. Thanks for the reply

I understand, thanks for the update!

---