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

 @rockfire Thanks for the refreshed patch, it's greatly appreciated.

 @DavidAnderson The presence of jobs in the wp-cron queue is being used as
 a proxy for determining whether cron is being run on the server.

 For sites using the default set up a loopback request to /wp-cron.php will
 be fired as the dashboard is opened. If the loopback request is working,
 any due jobs will be processed.

 For sites using crontab due jobs won't run until the next cron event is
 fired. The presence of due jobs does not indicate the site is not
 operating as the site administrator intends. The administrator may have
 switched to crontab because they have long running jobs that timeout over
 HTTP so must be run on the CLI.

 You are right, a recommended frequency should be documented alongside the
 constant to disable wp-cron loopback requests. I will contact the docs
 team.

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