[wp-trac] [WordPress Trac] #47223: Site Health Check: "last missed cron" test too aggressive
WordPress Trac
noreply at wordpress.org
Wed May 13 12:42:12 UTC 2020
#47223: Site Health Check: "last missed cron" test too aggressive
-------------------------------------------------+-------------------------
Reporter: DavidAnderson | Owner:
| peterwilsoncc
Type: defect (bug) | Status: closed
Priority: normal | Milestone: 5.3
Component: Site Health | Version: 5.2
Severity: normal | Resolution: fixed
Keywords: site-health has-patch has-unit- | Focuses:
tests commit |
-------------------------------------------------+-------------------------
Comment (by jetxpert):
@peterwilsoncc,
Thanks for the quick, stellar reply. Concise and helpful.
Please know that many hosting companies (e.g., SiteGround) are
discouraging their clients (especially those on shared plans) from setting
up Real Crons less than 30 minutes. Based on your input, therefore, it
appears we're going to continue to have these "failed to run" cron
messages on our dashboard and other "trigger" issues as well.
With all due respect, I would like to ask the wonder-folks at WordPress
consider adjusting the cron timing to 30 minutes -- or -- in a future WP
revision, allow users to manually adjust the timing for cron tasks (e.g.,
in 10 minute increments up to one hour).
Quite frankly, 10 minutes seems too short and may cause undue server load
-- with the implication of a temporary host shutdown -- until the cron is
adjusted back to 30 minutes or greater.
Last, can you explain again where the 10 minutes came from? Justification?
Would like to understand better the rationale.
Again, thank you and have an awesome day!
--
Ticket URL: <https://core.trac.wordpress.org/ticket/47223#comment:36>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list