Standard WordPress cron jobs aren’t reliable for precise timing because they require site traffic to run. If your site receives three visits a day, the internal cron only executes three times, delaying auction closures until a visit occurs. If there are no visits for several days, auction processing stalls until the next visitor hits the site.
Running maintenance tasks via background cron jobs is far better than relying on site visitors. This is why we recommend using a true system cron via crontab or an external service like EasyCron.
Then set this cron (use either wget or curl – whatever your hosting supports, just don’t use both at same time! – best is to consult with your hosting support):
/usr/bin/wget -q -O https://domain.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1OR
/usr/local/bin/curl --silent https://domain.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1You can also then disable internal WP cron in wp-config.php (however we recommend to leave it on, just in case):
define('DISABLE_WP_CRON', true);