The nanoPost Email Check plugin has not finished an automatic test within the expected time. This warning alone does not tell you whether your site can still send email. Start with a manual test, then check why the automatic tests are overdue.

The warning appears after more than twice your chosen interval without a completed scheduled check, counted from the last completion or the start of the schedule. With daily checks, that is more than 48 hours. A check may never have started, or it may have started and stopped with an error before recording a result.
First, check whether sending works
Open Tools > Email Check and press Send test now. Look for a new result and check the recipient mailbox.
If the test passes, the manual attempt succeeded, but automatic testing still needs attention: a manual test does not reset the overdue-check warning.
If the test fails, you have a sending problem as well. Use the error decoder if there is an error message, or the no-error checks if there is none.
If the page shows an error or no new result appears, note the time and tell your host. They can look for an error that stopped the test before it recorded a result.
For example, you may receive the manual test email while the last row marked Schedule is several days old. That shows why sending and automatic testing need separate checks.
Check Site Health
Go to Tools > Site Health and look for reports about late or failed scheduled events, or a failed loopback request. A loopback request is the server making a web request to its own site; WordPress uses one when starting scheduled work from a page visit.
A scheduling warning is useful evidence for your host. A loopback warning points them towards the server’s ability to reach its own site. If Site Health shows neither, the Email Check warning still needs investigating: a check can start and crash, leaving no finished result.
If the notice includes DISABLE_WP_CRON, tell your host that too. This setting disables the usual page-visit trigger for scheduled work. It can be intentional, provided the host has another way to start that work.
What to send your host
You can ask your host to investigate without editing files or using a terminal. Send the warning, the time of the last scheduled result, what happened when you ran a manual test, and any Site Health findings.
Ask them to check whether WordPress scheduled tasks are being started, and whether the Email Check task stops with an error. The task’s name is nanopost_email_check_run. If the host runs scheduling separately, ask them to check that job too.
When they have made a change, look for a new result marked Schedule under Tools > Email Check. A completed scheduled run resets the overdue condition even if the email test fails; a failed result then needs its own sending investigation. Check again after the next interval to confirm automatic runs continue.
The remaining sections explain the scheduling mechanism and give commands for someone who manages the server.
How WordPress starts scheduled work
WP-Cron is WordPress’s system for scheduled tasks, including Email Check’s automatic tests. In its usual configuration, a request that loads WordPress gives it a chance to look for work that is due. It starts that work with a separate request to wp-cron.php.
That makes a quiet site different from a clock-driven schedule: if no request reaches WordPress, a due task can wait. A cache that serves a page without loading WordPress does not trigger this check either. The request to wp-cron.php can also fail, for example if site-wide password protection blocks it.
A host can instead arrange for the server to start WordPress’s scheduled tasks regularly. This removes the dependence on page visits. It does not repair a task that starts successfully and then crashes.
Developer checks
Run these commands from the site’s WordPress directory with WP-CLI, the WordPress command-line tool:
wp cron test
wp cron event list
The first checks whether WP-Cron can start through its normal web request. The event list shows scheduled tasks and their next due times. Find nanopost_email_check_run and compare it with the last completed scheduled result in Email Check. If page-triggered cron is intentionally disabled, check the host’s replacement schedule rather than treating that setting alone as a fault.
A next-run time in the past means the event is overdue. A time in the future does not prove the previous run finished: WordPress schedules the next occurrence before executing the current one.
WP Crontrol offers a way to inspect scheduled events in the dashboard if you do not use WP-CLI.
When the check crashes
To investigate a check that starts but records no result, ask the host to read the PHP error log at the time it ran. PHP is the language WordPress and its plugins run in; a fatal error can stop execution before Email Check saves the outcome.
A developer can also run the task directly and watch the output:
wp cron event run nanopost_email_check_run
This attempts a real test email. An error naming a plugin file gives you a specific place to investigate. Fix that error and run the task again, then confirm a later automatic run also completes. Running it by hand verifies that invocation, not that the server will keep starting it on schedule.
Set up a server schedule
If page-triggered scheduling is the problem, ask your host to configure a server cron job, a task the server starts on a timetable. If you manage the server yourself, first check whether a job already exists.
For a server with WP-CLI, this example checks for due WordPress tasks every ten minutes:
*/10 * * * * cd /path/to/wordpress && /path/to/wp cron event run --due-now --quiet
Replace both paths with the real locations and run it under the site’s operating-system user. Each WordPress task retains its own interval; the ten-minute job only starts tasks that are due. WP-CLI does not depend on the loopback web request.
If WP-CLI is unavailable, the host can schedule a request to wp-cron.php instead, provided the URL is reachable:
*/10 * * * * curl --fail --silent --show-error 'https://example.com/wp-cron.php?doing_wp_cron' > /dev/null
Replace example.com with the site’s domain. Confirm that the new job runs successfully before disabling the page-visit trigger. Then, in wp-config.php, set the following above the line that says to stop editing, updating an existing definition if there is one:
define( 'DISABLE_WP_CRON', true );
Check for new scheduled results after the next Email Check interval.
WordPress’s server-scheduling instructions explain the configuration in more detail.
