Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


lal
  •  lal
  • No customer Topic Starter
2008-10-28T03:55:54Z
We just upgraded this weekend from VC 4.9.3 to 4.9.11.

Since the upgrade, we have encountered a problem with some jobs that don't trigger.

The trigger type is a time interval trigger, for jobs that run once a day.

I have confirmed that the trigger is active. I have checked the logs to confirm that VC did not attempt to run the job at all, and there are no errors at the scheduled job run time. There have been a number of application exceptions from various problems that caused VC restarts over the weekend, and I also confirmed that after the last VC restart prior to the scheduled job run time, the "next execution time" was correct for the jobs having this issue.

So far, I haven't been able to identify a significant difference between the jobs with a time interval trigger that are working normally, and the ones that have failed to trigger.

Any suggestions on how to fix the problem with the trigger?

Sponsor
Forum information
Support
2008-10-28T09:13:26Z
1. Did next run update after the time passed?
2. Did last last run update?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
lal
  •  lal
  • No customer Topic Starter
2008-10-29T03:40:07Z
I'm not sure, if you mean by checking the interface; we manually ran the job on the day that it didn't work, so it's been updated since then. I've noticed that when we have a lot of problems with VC restarts from application exceptions, the stated last run time in the interface is not always accurate, so I pay more attention to what I can find in the server log. Is there a way to see historically the updates to the next run and last run , beyond the most recent one that is displayed? I could check the backup xml files, but that would just be a snapshot at a specific time, rather than capturing each change to that field when it happened.

It seems that the affected jobs were only affected on the first scheduled run after the upgrade; on the following day's scheduled run, they triggered normally. It may take a week or so to make sure that this is true of all jobs, since some run less often than daily.
Support
2008-10-29T05:45:27Z
Could you please send us the server log file from the day it restarted to support@visualcron.com.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
ErikC
2008-10-29T10:09:53Z
Why are you not upgrading to the current latest stable version 4.9.26? This issue could be solved in there?

Regards
Erik
Uses Visualcron since 2006.
lal
  •  lal
  • No customer Topic Starter
2008-10-30T01:31:57Z
I'm sorry - I mispoke - the upgrade was to 4.9.26. Thanks.
Support
2008-10-31T12:07:40Z
Hi, we still need the feedback from you that we posted earlier.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top