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


MikeBoBo
2009-06-17T01:30:18Z
I have a job that pulls a graph every hour and emails it to us.

At 9am, the sent time on the email I recieved was correct.

I upgraded the server from 4.9.40 to 5.1.6.

At 10am, the sent time on the email was 6am, not 10am.

I can't see anyway to change this in VC.
Sponsor
Forum information
Support
2009-06-17T13:02:36Z
It is hard to say. You should check in the log when the Notification or Email Task was sent. We do not alter the actual sent time.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
MikeBoBo
2009-06-17T14:34:31Z
It was actually sent at the time it was supposed to have been, 10am.

This only occurred after the upgrade to 5.1.6.
Support
2009-06-17T14:45:00Z
Maybe the mail server holds the final answer. When the message arrived. Because, we don't set this value at all.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
MikeBoBo
2009-06-18T22:30:18Z
This only seems to happen with Mail tasks, not mail notifications.

It was working without issue before 5.1.6 and nothing else has changed in the enviroment.

I validated this in a different enviroment using a different incoming and outgoing server.

This is an issue with 5.1.6 and email tasks.
MikeBoBo
2009-06-18T22:56:04Z
Header info below.

I don't understand why there are 2 different applications being used for notification/tasks but I suspect the real issue is the date line on the Task. This should probably read GMT time, not "local time --0700"


Notification:

Date: Thu, 18 Jun 2009 20:26:01 GMT
X-Mailer: OpenSmtp.net
X-OriginalArrivalTime: 18 Jun 2009 20:26:00.0228 (UTC) FILETIME=[FE5D4640:01C9F052]


Task:

MIME-Version: 1.0
X-Mailer: EldoS SecureBlackbox, version: 2006.09.18
Date: Thu, 18 Jun 2009 13:26:00 --0700
X-OriginalArrivalTime: 18 Jun 2009 20:25:59.0743 (UTC) FILETIME=[FE1344F0:01C9F052]
MikeBoBo
2009-06-22T17:29:58Z
Any progress on this?

It's quite a big issue for us.
Support
2009-06-22T23:33:28Z
We have now confirmed this as a bug. Thank you for the report. We will get back to you when this is fixed. Hopefully within a week.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Support
2009-07-09T22:48:34Z
This is now fixed in 5.2.1 - please confirm this. It can be downloaded from beta forum.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
MikeBoBo
2009-07-10T00:47:28Z
Confirmed resolved.

Do you have a timeline on this going gold?
Support
2009-07-10T09:23:44Z
Probably next week if nothing special is found. Thanks for the confirmation.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top