[Solved] Next Run Times Are Incorrect - VisualCron

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

Welcome Guest! To enable all features please Login or Register.

keithdavis
Free support Topic Starter

2014-01-29T13:35:57Z

In the List, many, if not all, of the Next Run times (not dates) are incorrect.

These are a sample of the ones that I know for sure.

Edited by moderator 2014-03-19T08:54:52Z | Reason: Not specified

keithdavis attached the following image(s):

Sponsor

Forum information

Wanna join the discussion?! Login to your Forum forum account or Register a new forum account

keithdavis
Free support Topic Starter

2014-01-29T13:46:52Z

Ok, I just updated 1 trigger for one job, then closed and re-opened the client and now they are all correct. However, this is not the first time I've seen this happen.

Support
Official support

2014-01-29T14:02:01Z

In what way are they incorrect? (I see that they are in the future)

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

keithdavis
Free support Topic Starter

2014-01-29T14:04:13Z

Everyone of those examples are daily, or weekly jobs and the start time is always the same and so in those examples the Next Run time (not date), should be same as the Last Run time (not date.)

Support
Official support

2014-01-29T15:27:21Z

So, the actual time has been shifted 6 hours?

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

keithdavis
Free support Topic Starter

2014-01-29T15:51:17Z

Correct. Ah, that's a the time-zone difference. So, at times, the List is not using the correct time-zone?

Support
Official support

2014-01-29T17:38:40Z

Is the server not in the same time zone as the client?

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

keithdavis
Free support Topic Starter

2014-01-29T17:40:59Z

No, all clients and servers are in the same time-zone (same city.)

Support
Official support

2014-01-29T17:42:50Z

Do you have one Job which has not updated that value yet? If so, please add a screenshot of the Trigger settings.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

keithdavis
Free support Topic Starter

2014-01-29T18:22:52Z

#10

Actually, yes, it's doing this again and now, I'm on a client in the same building as the server.

keithdavis attached the following image(s):

keithdavis
Free support Topic Starter

2014-03-18T17:50:54Z

#11

All of these times are off by 5 hours.

Version 7.1.3

keithdavis attached the following image(s):

bbusse
No customer

2014-03-18T19:11:36Z

#12

Originally Posted by: keithdavis

Actually, yes, it's doing this again and now, I'm on a client in the same building as the server.

Just for the sake of asking.. and hopefully it hasn't been already.. Have you literally checked the Timezone configuration on both the server and the client machine just to be sure. I realize it's 99.9% likely that they are in fact both configured for the same timezone... and have the correct time. Just asking because all that was stated is that they're in the same building, which doesn't mean same config.

Brian

Edited by user 2014-03-18T19:16:35Z | Reason: I said same room, i meant same building

keithdavis
Free support Topic Starter

2014-03-18T19:19:22Z

#13

Yes. Also, if I edit one of those entries, that entry, upon refresh, shows the correct time.

bbusse
No customer

2014-03-18T19:26:01Z

#14

Originally Posted by: keithdavis

Yes. Also, if I edit one of those entries, that entry, upon refresh, shows the correct time.

Any ryhme or reason you can determine that leads to showing the wrong date? As in... anything I could try to do to reproduce it on mine? I've tried with 7.1.1 and 7.1.4 (what I have currently installed), have not tried with 7.1.3 yet.

Brian

Support
Official support

2014-03-19T08:52:21Z

#15

I think this case has been resolved.

Here is the feedback from the file we got from Keith:

We examined the log and found that VisualCron did not receive a TimeChanged event from the system. We are not sure why. We had a fallback for that but it did not work properly. We have made a change in this fallback for the next version and hopefully you should not experience this again. The fix was made in the upcoming 7.1.4.

I should have closed this earlier with the information. Sorry.

Edited by user 2014-03-19T08:54:36Z | Reason: Not specified

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

keithdavis
Free support Topic Starter

2014-03-19T12:59:01Z

#16

Originally Posted by: Support

I think this case has been resolved.

Here is the feedback from the file we got from Keith:

We examined the log and found that VisualCron did not receive a TimeChanged event from the system. We are not sure why. We had a fallback for that but it did not work properly. We have made a change in this fallback for the next version and hopefully you should not experience this again. The fix was made in the upcoming 7.1.4.

I should have closed this earlier with the information. Sorry.

I'm confused. Aren't your referring to this post?

http://www.visualcron.co....aspx?g=posts&t=3877

Or are you saying these two are related?

Support
Official support

2014-03-19T18:39:09Z

#17

Maybe I am confused but a result of something not executing according to schedule is that next runtime values are not updated properly. To start recalculation again there are the following ways:

1. click Stop server and then Start in Client
2. edit a Job
3. activate or deactivate a job
4. restart the whole VisualCron service

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

bbusse
No customer

2014-03-19T18:46:09Z

#18

Down in the bottom left of the VisualCron client window, you have the Server name, and Server time. I assume this time matches the 'correct' time, even though you see a job saying the next runtime is 6 hours off. Now, other than looking like a job scheduled for 7:30am.... having a next runtime listed as 1:30pm, does it actaully run at 7:30am or is it really waiting until 1:30pm to run?

Brian

keithdavis
Free support Topic Starter

2014-03-19T18:46:35Z

#19

Originally Posted by: Support

Maybe I am confused but a result of something not executing according to schedule is that next runtime values are not updated properly. To start recalculation again there are the following ways:

1. click Stop server and then Start in Client
2. edit a Job
3. activate or deactivate a job
4. restart the whole VisualCron service

But I don't believe this issue is affecting the actual run times, only what is displayed at times. I have evidence that these jobs are running at the correct times.

keithdavis
Free support Topic Starter

2014-03-19T18:48:27Z

#20

Originally Posted by: bbusse

Down in the bottom left of the VisualCron client window, you have the Server name, and Server time. I assume this time matches the 'correct' time, even though you see a job saying the next runtime is 6 hours off. Now, other than looking like a job scheduled for 7:30am.... having a next runtime listed as 1:30pm, does it actaully run at 7:30am or is it really waiting until 1:30pm to run?

Brian

Well, right now it's working. It doesn't do this all the time. Also, we upgraded to 7.1.4 yesterday, FYI.

keithdavis attached the following image(s):