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
Cron entries are stored in an array, sorted by their next activation time. Cron
sleeps until the next job is due to be run.
Upon waking:
it runs each entry that is active on that second
it calculates the next run times for the jobs that were run
it re-sorts the array of entries by next activation time.
it goes to sleep until the soonest job.
The important part is the last line. The Cron will go to sleep until the next job is due. So this isn't exactly a bug but wanted behavior.
Maybe the package should consider some catching mechanic for system clock change events?
Hello All , I have encounter an issue.
we can get issue when we do step as follow:
-------------when time MM:SS get, bug job can't start-------------
The text was updated successfully, but these errors were encountered: