[wp-trac] [WordPress Trac] #47223: Site Health Check: "last missed cron" test too aggressive

[WordPress Trac]

#47223: Site Health Check: "last missed cron" test too aggressive
-------------------------------------------------+-------------------------
 Reporter:  DavidAnderson                        |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Site Health                          |     Version:  5.2
 Severity:  normal                               |  Resolution:
 Keywords:  site-health needs-testing has-patch  |     Focuses:
-------------------------------------------------+-------------------------

Comment (by DavidAnderson):

 Why should the determination of whether a cron job is "late" depend upon
 the method being used to invoke cron jobs? This is over-complicating
 things. A job is either sufficiently late for it to be worth advising the
 user about it, or it isn't. If I turn up late for work, that's all the
 boss cares about - "but I decided to walk, slowly" doesn't mean that late
 is no longer late.

 As a plugin developer who uses cron in several plugins, I see that lots of
 people disable the "loopback" cron mechanism and use something else, and
 set up that something else to call `wp-cron.php` far too infrequently
 relative to the number of cron jobs on their site. We shouldn't add
 allowances for that. If a job is sufficiently late to advise of at all,
 the user should be advised. And correspondingly, if it's decided that 15
 minutes late is OK for some users, then it's OK for all. Or alternatively,
 if it really is intended that different cron methods are meant to work
 differently, this should be documented.

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