gronx Not firing task due

I have a task specified as */10 8-12 * * 1-5 and ran the application exactly at 12:10 on a Thursday. Yet it did not consider it due, despite the fact it was listed as such previously using the NextTick() method

Aug 21 '25 17:08 lordofscripts

Apparently, if the code is not executing exactly at the ZERO second of that minute, the due attribute is not set, so basically it will never see it as due unless you are very lucky.

Aug 21 '25 20:08 lordofscripts

It would be nice if it had a user option to use minute precision instead of the default seconds precision.

Aug 21 '25 21:08 lordofscripts

sorry for late, if all the cron expressions are fulfill-able by minute precision then minute is used instead of second: https://github.com/adhocore/gronx/blob/main/pkg/tasker/tasker.go#L285

https://github.com/adhocore/gronx/blob/main/pkg/tasker/tasker.go#L261

Oct 21 '25 07:10 adhocore

sorry for late, if all the cron expressions are fulfill-able by minute precision then minute is used instead of second: https://github.com/adhocore/gronx/blob/main/pkg/tasker/tasker.go#L285

https://github.com/adhocore/gronx/blob/main/pkg/tasker/tasker.go#L261

Then what would be wrong with the spec I used above?

Oct 23 '25 16:10 lordofscripts