[wp-trac] [WordPress Trac] #57271: Cron unschedule / reschedule event errors

[WordPress Trac]

#57271: Cron unschedule / reschedule event errors
----------------------------------------+------------------------------
 Reporter:  domainsupport               |       Owner:  audrasjb
     Type:  defect (bug)                |      Status:  assigned
 Priority:  normal                      |   Milestone:  Awaiting Review
Component:  Cron API                    |     Version:  6.0
 Severity:  normal                      |  Resolution:
 Keywords:  has-patch needs-unit-tests  |     Focuses:
----------------------------------------+------------------------------

Comment (by chargeup):

 Thinking out loud. If the cron job is set on the server for this domain
 http://domain.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1 then redirects
 to https://www.domain.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1 could
 that also cause a concurrent request? Just mentioning this as a possible
 cause in those cases for the concurrent request theory.



 Replying to [comment:9 domainsupport]:
 > Replying to [comment:8 peterwilsoncc]:
 > > > One theory I had was concurrent requests to a WordPress installation
 from different hostnames (with and without "www." or with and without SSL
 for example, they don't have to be completely different domains) firing
 the same cron event?
 > > `wp-cron.php` sets a transient in order to prevent events running in
 this manner but this might be possible if the time between two requests is
 very quick or if the site is running a plugin that disable transients.
 >
 > I'd forgotten about this comment where he says he's not a high traffic
 site and his cron is set to run by the system so does that not rule out
 the concurrent request theory? https://wordpress.org/support/topic/cron-
 unschedule-event-error-for-hook/page/2/#post-16255896
 >

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