WP-Cron Status Checker Pro: Are Scheduled Hooks Completing?

WP-Cron runs background work such as scheduled posts, update notices, auto-draft cleanup, subscription billing, session cleanup, and scheduled sales. If it cannot run, these tasks may not happen as expected. WP-Cron Status Checker Pro displays status in the WordPress dashboard and logs results for hooks that run through WP-Cron.

Availability: a check independent of WP-Cron

Every 24 hours, the extension checks whether WordPress can run WP-Cron. It sets its own transients to expire over that period, so the check does not depend on WP-Cron itself. When a transient expires, the extension runs the check. An unexpected error triggers an email notification.

Hook results: timing and completion

Hook logs record what ran, when it ran, how long it took, and whether it completed. A hook that takes longer than five minutes is treated as failed. The plugin also tries to detect some cases where code abruptly exits the process. Depending on what it detects, the elapsed time may appear as N/A with an Incomplete status, or the result may show Exit, which is considered complete.

Two error messages, different likely causes

A message that WP-Cron cannot run usually points to WordPress, the server, or permissions. A message that WP-Cron failed to complete usually points to specific PHP code that produced an error or did not finish. The message can help narrow down where to investigate.

Pro log history and email options

WP-Cron Status Checker Pro removes the three-log limit and lets you keep logs longer and receive emails more frequently. Choose the available log-retention and email-frequency settings to fit how you review scheduled activity. Failure notices are sent within 24 hours or according to the plugin settings.

Find status and review logs

The status display appears on the WordPress admin dashboard. Open Tools, then WP Cron Status, to view the status page. After installation, review the log and email settings, pick how long to keep logs and how frequently to receive emails, then use the logs to inspect hook results, durations, and completion statuses.