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?
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?