You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: