Email Check: when the checks stop

The notice says the last check is older than twice the schedule interval. The checks are not failing: they are not running. Email Check runs its checks on WP-Cron, WordPress’s built-in scheduler, and WP-Cron has stopped running them. Whatever stopped them is also delaying every other scheduled job on the site: scheduled posts, update checks, and other plugins’ background work.

How WP-Cron runs

WP-Cron is not a clock. It runs when someone loads a page. On each normal page request, WordPress checks whether any scheduled job is due. If one is, then at the end of that request WordPress sends a request to its own wp-cron.php (a loopback request: the server calling its own site), and that request runs the due jobs.

So a scheduled job needs two things: a page request that reaches WordPress, and a loopback request that gets through.

Why it stops

  • No requests reach WordPress. On a site with few visitors, jobs run late. On a site behind a full-page cache (a host cache, a caching plugin, or a CDN that caches HTML), most visits are answered by the cache and never reach PHP, so WP-Cron gets no chance to run.
  • DISABLE_WP_CRON is on, with nothing to replace it. The constant in wp-config.php stops page requests from starting WP-Cron. It is meant to be paired with a server cron job. After a move to a new host, the constant often comes along and the cron job does not.
  • The loopback request fails. Password protection on the whole site (HTTP basic auth), a firewall or security plugin that blocks the server’s requests to itself, or a domain that does not resolve from the server all stop wp-cron.php from being reached.

Find out which

  • Site Health. Tools > Site Health reports “A scheduled event is late”, “A scheduled event has failed”, and loopback request failures.
  • WP-CLI. wp cron test checks that WP-Cron can start. wp cron event list lists every scheduled job and when it is next due. Email Check’s job is nanopost_email_check_run; a next-run time in the past means the job is overdue.
  • A plugin. WP Crontrol lists scheduled jobs in wp-admin and marks the ones that are late.
  • wp-config.php. Look for define( 'DISABLE_WP_CRON', true );.

Use a real cron job

A server cron job runs WP-Cron on a fixed timetable, whatever the traffic or the cache. Most hosts offer cron jobs in the control panel; on a VPS, use crontab -e.

  1. Add the cron job first. Run due jobs every 10 minutes, with WP-CLI if the host has it:

    */10 * * * * cd /path/to/wordpress && wp cron event run --due-now --quiet

    or with a plain request to wp-cron.php:

    */10 * * * * curl -s https://example.com/wp-cron.php?doing_wp_cron > /dev/null

    The WP-CLI form does not depend on a loopback request, so it also works when the loopback is blocked.

  2. Then stop page requests from starting WP-Cron. Add this to wp-config.php, above the line that says to stop editing:

    define( 'DISABLE_WP_CRON', true );

The notice clears after the next check passes. Send test now does not use WP-Cron, so it shows that sending works, not that the schedule does. Wait for the next scheduled check, or run wp cron event run nanopost_email_check_run to start it at once.