AdTempus not triggering the jobs on selected schedule when TimeZone is used - Community

April 17, 2014 02:39 PM

Accepted Answer

Can someone please advise on the issue described below: I am trying to schedule an AdTempus job to run 3 days per week (Tuesday, Thursday, Saturday) at a specific time.

I also want the job to run on a specific Time Zone (UTC -06:00), different from the Time Zone where the job is being executed (UTC -05:00). The job executed on Thursday (4/17/2014), and the next run should be Saturday (4/19/2014). AdTempus console shows that Next Start is tomorrow (4/18/2014). I

have attached a screenshot.

Version: adTempus 4.0.0

OS: Windows 7 Professional (Service Pack 1)

Thanks,

Edison

Attachments

Capture.PNG (0b)

Bill Staff (599 posts)

May 5, 2014 08:39 AM

Accepted Answer

We have confirmed a problem that causes jobs to sometimes run on the wrong day if the Schedule Trigger uses a time zone other than the default. The problem has been fixed for version 4.0.3.

Jonathan Qiu (2 posts)

May 14, 2014 11:27 AM

Accepted Answer

Hi Bill,

According to adTempus 4 download web page (http://www.arcanadev.com/adtempus/download.aspx), the latest released version is 4.0.2. Can you please let us know when the version 4.0.3 will be released?

Bill Staff (599 posts)

May 14, 2014 04:22 PM

Accepted Answer

This should be out next week. You can open a support case if you want to get a hotfix release now that contains the fix.

Jonathan Qiu (2 posts)

May 29, 2014 03:13 PM

Accepted Answer

We'd like to use version 4.0.3 instead of the hotfix for version 4.0.2. Can someone provide the release day for this version?

Bill Staff (599 posts)

May 29, 2014 03:20 PM

Accepted Answer

The release got delayed to accommodate some additional changes, but testing is wrapping up and it should (again) be out next week.

Bill Staff (599 posts)

June 9, 2014 09:30 AM

Accepted Answer

This fix is now available in adTempus 4.1.