I have a job scheduled using an interval trigger set to last day of every month. If I run the job manually it successfully updates the next run date. However if it is run automatically based on the trigger, the next run date is no longer updated correctly. Rather than setting the next run date to the last day of the next month, it instead always sets it to the month after the original start time.

For instance, the original start time for the trigger is 5/31/2008. When the program ran on 12/31/2008, rather than update the next run to 1/31/2009, it set it to 6/30/2008. However, as stated earlier, if I run the job myself, it correctly updates the next run to 1/31/2009.

Thanks.

Hi,

we will test this through and get back to you. Thanks for reporting.

---

Which settins did you use exactly? Specific days of the month? Please gives us all details including exact start time May 31.

---

The settings for the trigger are as follows:

Interval: Specific days of the month
Every: 1 Month(s)
'Last day of the month' radio button is selected

Start time: 5/31/2008 4:00:00AM

---

On the bottom of the trigger screen described above the next run date says 6/30/2008 4:00:00AM, but on the main job screen it says 2/28/2009 4:00:00AM (the correct date since I ran it manually last time). So it appears that when the trigger kicks off the program it updates the 'next run' with the value shown on the trigger screen which is incorrect.

Thank you for your assistance in researching this matter.

Thanks for the information. We believe we have reproduced and fixed the issue. It will be fixed in the next beta 4.9.58. which will be posted later today in the beta forum.

---

Ok sounds good. I will probably install it later this week. Thanks for all your help!