[wp-trac] [WordPress Trac] #44818: cron: preventing duplicate events fails when the first event is too far in the past

[WordPress Trac]

#44818: cron: preventing duplicate events fails when the first event is too far in
the past
-----------------------------+------------------------------
 Reporter:  bodohugobarwich  |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Cron API         |     Version:  4.9.8
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+------------------------------

Comment (by bodohugobarwich):

 Yes, it adds a restriction to the functionality that a new event must be
 at least 10 min after the last event.\\
 So if you wanted to schedule events for the whole week you would schedule
 them from the first on Monday to the last on Sunday.\\

 I found that many plugins and even the Wordpress Core with the
 {{{do_ping}}} task do rely on the restriction that too close scheduled
 events would be rejected therefore I could observe scheduled event of the
 same type in 1 second interval if they were not rejected.

 I'm not aware where the 10 Minutes Limit does come from but redefining it
 reasonably would help to easy the confict.\\
 Unix Systems do normally treat the scheduled events in 1 Minute Interval
 so that would be a useful Starting Point.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/44818#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform