[wp-trac] [WordPress Trac] #39924: wp_schedule_single_event is possibly failed to schedule a task when it is called concurrently

[WordPress Trac]

#39924: wp_schedule_single_event is possibly failed to schedule a task when it is
called concurrently
--------------------------+------------------------
 Reporter:  hainey        |       Owner:
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Cron API      |     Version:
 Severity:  normal        |  Resolution:  duplicate
 Keywords:                |     Focuses:
--------------------------+------------------------
Changes (by dd32):

 * status:  new => closed
 * resolution:   => duplicate
 * version:  4.6 =>
 * component:  General => Cron API
 * milestone:  Awaiting Review =>


Comment:

 Hi @hainey and welcome to Trac,

 Unfortunately race conditions such as this are a well known (amongst some)
 issue with WordPress's cron system - It's not designed to be used in a
 scenario where it's likely events are to be registered in such a way that
 a race condition could be hit.

 This is a duplicate of #13158, however you may also be interested in
 #15148. There exist alternative storage options for WordPress cron events
 though, one such option that I use (and WordPress.org also uses) is
 [https://github.com/humanmade/Cavalcade Cavalcade] - a separate daemon
 which runs on the server on top of wp-cli and guarantees (more or less)
 that jobs get scheduled and run.

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