- This topic has 3 replies, 2 voices, and was last updated 3 years, 10 months ago by .
Viewing 1 reply thread
Viewing 1 reply thread
- You must be logged in to reply to this topic.
Hello Kim
I found that when using then Scheduler with Cron and mwscmExtendedSecond the first element is treated as minutes instead of seconds, if I instead use mwscmExtendedSecondAndYear then it works as expected.
Best regards
Job Espejel.
Update:
Cron and seconds are not working correctly, even with mwscmExtendedSecondAndYear
Please try something like
*/45 * * * * * *
/45 * * * * * *
45 * * * * * *
or
0 */1 * * * * *
I give up trying to make it work with seconds.
Reverting to the default format.
Regards
Job Espejel
Hi,
You are right. There is a bug.
The fix:
Find function TkbmMWScheduleRange.GetInterval and make sure it looks like this:
function TkbmMWScheduleRange.GetInterval:integer; begin case FType of mwsrtValues: begin Result:=kbmMWGCD(FValues) div 2; if Result=0 then Result:=1; end; else Result:=1; end; end;
It is fixed in next release.