I switched to using a monthly interval for this particular case. It turns out the basic issue is that when scheduling, say, a monthly interval, a specific day of the month is entered. But instead of using that information to determine the next scheduled execution time, it is using the last time the task ran (e.g., Test Run) plus the selected interval (a month in this case).

The code below is from ExecRuleHelper.php. Based on the comments, it appears to be unfinished. Clearly in the case for 'interval', no attempt to use the specified day-of-month is made. The $nextExec is clearly only ever based on $lastExec.

/**
 * @param   boolean  $string    If true, an SQL formatted string is returned.
 * @param   boolean  $basisNow  If true, the current date-time is used as the basis for projecting the next
 *                              execution.
 *
 * @return ?Date|string
 *
 * @since  4.1.0
 * @throws \Exception
 */
public function nextExec(bool $string = true, bool $basisNow = false)
{
    // Exception handling here
    switch ($this->type) {
        case 'interval':
            $lastExec = Factory::getDate($basisNow ? 'now' : $this->getFromTask('last_execution'), 'UTC');
            $interval = new \DateInterval($this->rule->exp);
            $nextExec = $lastExec->add($interval);
            $nextExec = $string ? $nextExec->toSql() : $nextExec;
            break;
        case 'cron-expression':
            // @todo: testing
            $cExp     = new CronExpression((string) $this->rule->exp);
            $nextExec = $cExp->getNextRunDate('now', 0, false, 'UTC');
            $nextExec = $string ? $this->dateTimeToSql($nextExec) : $nextExec;
            break;
        default:
            // 'manual' execution is handled here.
            $nextExec = null;
    }

    return $nextExec;
}

The workaround until the above code is completed is to edit the database table #_scheduler_tasks and set next_execution to the date/time you want after any test run.

As for the cron-expression case, I am not sure what the issue was there but it is likely it's similar to the interval case. This code just does not appear to be finished yet.

I have made a fix (#44061) for the interval, would be great if you have time to test it. I have also looked at the cron-execution and it seems to me doing it in the right way, not tested all possibilities. There are some things I would do different, but that is more the UI that functionality.

I think the cron-execution may have been worked on since I created my
ticket.

I'll give it a workout this weekend and get back to you. It looks like I
have the ability to approve the change, but I have never done so. Please
advise on next steps after testing.

Thanks!
Bruce

Bruce Scherzinger ** b
@.>@.**
@.**>

On Thu, Sep 12, 2024 at 7:18 AM Robert Deutz @.***>
wrote:

I have made a fix (#44061
#44061) for the interval,
would be great if you have time to test it. I have also looked at the
cron-execution and it seems to me doing it in the right way, not tested all
possibilities. There are some things I would do different, but that is more
the UI that functionality.

—
Reply to this email directly, view it on GitHub
#42459 (comment),
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD3BBERKIVPAC3SO4A5L4H3ZWFZ7FAVCNFSM6AAAAABAFEUSYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBWGAYTKMBVGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hey Robert, here are my observations.

• On Sep 13, saved an existing monthly task that is scheduled to run on
  the 20th of every month. Now it shows the next execution will be on Oct 20,
  not Sep 20 as it should be. But it did get the time correct.
  • Maybe if one could edit the Next Scheduled Execution, this would
    provide a temporary workaround. Currently, this requires a database
    modification.
• The cron scheduler UI does not allow selections in multiple interval
  groups. For instance, if I select day 20, when I try to select any month,
  the day becomes unselected. This is clearly a UI issue and it prevents me
  from testing cron scheduling. Note that I started with J! 5.1.4 and simply
  replaced the code you modified.
• The interval-days option computes next execution time as expected.
• The interval-minutes and -hours seem to work fine. But it would be
  nice to be able to specify the minute within the hour for
  interval-hours, similar to how you can specify the hour for interval-days.
  I suppose this is really what cron scheduling is for, but that's not usable
  in J! 5.1.4.

It has been my observation that the next execution time is honored by the
task scheduler. So my testing here was focused on making sure that time is
set correctly in each case. It seems we still have an issue with the cron
scheduler (seems like a UI issue) that may already be fixed in 5.2. But the
fact the interval-months computation is going a month past the next
occurrence is an issue with these changes.

Hope this helps.

Regards,
Bruce

Bruce Scherzinger ** b
@.>@.**
@.**>

On Thu, Sep 12, 2024 at 5:33 PM Bruce Scherzinger <
@.***> wrote:

I think the cron-execution may have been worked on since I created my
ticket.

I'll give it a workout this weekend and get back to you. It looks like I
have the ability to approve the change, but I have never done so. Please
advise on next steps after testing.

Thanks!
Bruce

---

Bruce Scherzinger ** b
@.>@.**
@.**>

On Thu, Sep 12, 2024 at 7:18 AM Robert Deutz @.***>
wrote:

I have made a fix (#44061
#44061) for the interval,
would be great if you have time to test it. I have also looked at the
cron-execution and it seems to me doing it in the right way, not tested all
possibilities. There are some things I would do different, but that is more
the UI that functionality.

—
Reply to this email directly, view it on GitHub
#42459 (comment),
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD3BBERKIVPAC3SO4A5L4H3ZWFZ7FAVCNFSM6AAAAABAFEUSYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBWGAYTKMBVGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Oh, I forgot something.
When I do a Run Test, that resets the next execution time for the minutes
and hours cases, but not for the others. IMHO, Run Test should NEVER change
the next execution time.

Bruce Scherzinger ** b
@.>@.**
@.**>

On Fri, Sep 13, 2024 at 7:06 PM Bruce Scherzinger <
@.***> wrote:

Hey Robert, here are my observations.

• On Sep 13, saved an existing monthly task that is scheduled to run
  on the 20th of every month. Now it shows the next execution will be on Oct
  20, not Sep 20 as it should be. But it did get the time correct.
  • Maybe if one could edit the Next Scheduled Execution, this would
    provide a temporary workaround. Currently, this requires a database
    modification.
• The cron scheduler UI does not allow selections in multiple interval
  groups. For instance, if I select day 20, when I try to select any month,
  the day becomes unselected. This is clearly a UI issue and it prevents me
  from testing cron scheduling. Note that I started with J! 5.1.4 and simply
  replaced the code you modified.
• The interval-days option computes next execution time as expected.
• The interval-minutes and -hours seem to work fine. But it would be
  nice to be able to specify the minute within the hour for
  interval-hours, similar to how you can specify the hour for interval-days.
  I suppose this is really what cron scheduling is for, but that's not usable
  in J! 5.1.4.

It has been my observation that the next execution time is honored by the
task scheduler. So my testing here was focused on making sure that time is
set correctly in each case. It seems we still have an issue with the cron
scheduler (seems like a UI issue) that may already be fixed in 5.2. But the
fact the interval-months computation is going a month past the next
occurrence is an issue with these changes.

Hope this helps.

Regards,
Bruce

---

Bruce Scherzinger ** b
@.>@.**
@.**>

On Thu, Sep 12, 2024 at 5:33 PM Bruce Scherzinger <
@.***> wrote:

I think the cron-execution may have been worked on since I created my
ticket.

I'll give it a workout this weekend and get back to you. It looks like I
have the ability to approve the change, but I have never done so. Please
advise on next steps after testing.

Thanks!
Bruce

---

Bruce Scherzinger ** b
@.>@.**
@.**>

On Thu, Sep 12, 2024 at 7:18 AM Robert Deutz @.***>
wrote:

I have made a fix (#44061
#44061) for the interval,
would be great if you have time to test it. I have also looked at the
cron-execution and it seems to me doing it in the right way, not tested all
possibilities. There are some things I would do different, but that is more
the UI that functionality.

—
Reply to this email directly, view it on GitHub
#42459 (comment),
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD3BBERKIVPAC3SO4A5L4H3ZWFZ7FAVCNFSM6AAAAABAFEUSYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBWGAYTKMBVGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>