cron icon indicating copy to clipboard operation
cron copied to clipboard

subsecond scheduling for "@every"

Open gezimblliku opened this issue 1 year ago • 1 comments

Since subsecond scheduling is not supported even when using @ every, I forked the subject to remove the second limit (mostly to prevent long unit tests). I wanted to know the reason why this limitation is added first place,to prevent any degradation of performance or any potential misschedule of jobs?

gezimblliku avatar Oct 30 '24 10:10 gezimblliku

Subsecond schedule can be manually entered into actual definition of minute job . This will avoid over engineering of matured library

ivikasavnish avatar Jan 07 '25 09:01 ivikasavnish