[wp-trac] [WordPress Trac] #47223: Site Health Check: "last missed cron" test too aggressive
WordPress Trac
noreply at wordpress.org
Thu May 30 22:43:51 UTC 2019
#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: Administration | Version: 5.2
Severity: normal | Resolution:
Keywords: needs-patch site-health | Focuses:
-------------------------------------+-----------------------------
Comment (by Clorith):
Good thoughts, I'm curious what might be the best approach here, I'd not
experienced a failed cron report my self, so I hadn't thought of it as
being too strict, but I definitely see the potential as you've all
mentioned.
The check is clearly going to need a few more conditions, which isn't a
problem at all, we want this to be as accurate as possible, or else
there's little use to it :)
Are there other scenarios the cron check needs to be aware of than the
ones outlined already?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/47223#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list