I went to look at a job log for one that I know is having trouble (the issue is not related to this problem,it's a HTTP problem), but I can only see one job log entry and that is for today, but I know this job failed yesterday and it runs every day at 2AM.

Why does the log not pull up?

Probably because the history settings are limited. Go to Server tab->Settings->Log->DB and change number of days or entries to keep.

---

What is the deal with this forum? I get duplicate emails for replies or none...this time I got none. I just remembered to go check it, because, here is another example:

I've got a job that was "stuck", and said the last run time was 3/17, but when I pulled the log it shows events for 3/10 and 3/8, but nothing for 3/17.

Probably because the history settings are limited. Go to Server tab->Settings->Log->DB and change number of days or entries to keep.

So all of my settings are the default for all logs (2000 rows, 14 days.) Are you saying that my log if generating more than 2000 rows a day? How would I ever know what to set that at?

Ok, that server has a LOT of jobs. I changed it to 10,000 rows and 14 days. What is the maximum of rows? I care only about the days, but I undersand that there could be some kind of performance problem if I just set it to 5 million so that I could be assured that I would get 14 days.

I would uncheck "number of rows" and set it to 14 days. Should not be a problem but after a week you should check the statistics on the settings just to see that there is no "obscene" value.

---

Again, the need to be able to configure these settings for all servers at once! Love to see that Master / Slave feature that was proposed. Having to configure 10 servers every time we make a change is a pain.

Oh, and got the last reply email from the forum.

Love to see that Master / Slave feature that was proposed. .

Yes, we will start working on this during spring/summer.

---

I just realized that Extended Debug Logging was enabled on that server, probably to resolve some other issue. That is probably the cause, eh?

I just realized that Extended Debug Logging was enabled on that server, probably to resolve some other issue. That is probably the cause, eh?

Yes, it could as it generates a lot more logging.

---

I will post my problem here, bacause I feel it it's related some kind to this topic.

Recently we upgrated VisualCron to version 9.1.5 on a few servers. On some of them, we noticed that VC don't keep logs for tasks. In settings - options for task log is unusable and logs are 0. I'm attaching sreenshot. Also, if I choose task log from right click on the task I get dates from 2018y.
We are using this version and tested it from a long period of time and didn't face this kind of problem up to now, thats why we choose it as a last stable version to migrate to.