[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 peterwilsoncc):

 Hi @bodohugobarwich and welcome to trac!

 If I understand correctly, you're saying that having an event scheduled in
 the past - for whatever reason - then the 10 minute limit does not apply.

 For example, the `my_cron_hook` schedule could be:

 - `1/1/2016 12:00:00`
 - `1/1/2028 12:00:00`

 The bug is that a developer could then schedule `my_cron_hook` within a
 second of one of the future at `1/1/2018 12:00:01`.


 Please correct me if I have misunderstood.

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