• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

Question Make wp-cron.php run every minute

macandcheese

New Pleskian
Currently, when enabling 'Take over wp-cron.php' and 'Create a replacement task (...)', the cron job that's created only runs twice an hour. (See screenshots below)

This seems wrong; any Wordpress cronjob that needs to run at a higher interval, will fire too late.
There is no performance benefit to running wp-cron less often, in fact, it might cause performance problems, because late jobs would pile up.

We have a bunch of sites that needed their cronjobs to be manually tweaked due to this.

Can the default wp-cron.php interval be changed to every minute, please?

One source that offers some more explanation: Event Scheduling and wp-cron - Support Center
Missed crons and crons that run too frequently can both be resolved by enabling the [system native cronjob]. This alternate cron is a service on the server itself and checks for “due now” crons every minute by curling wp-cron.php, rather than running cron processes based on traffic flow.




1716866909673.png
1716866912504.png
1716866943217.png
 
Back
Top