

Scheduled Events: every WP-Cron event with its owner, last run and recent-run sparkline.
WordPress runs background tasks, called cron jobs, for things like publishing scheduled posts,
sending emails and running backups. It keeps no record of them, so when one fails or stops you
never find out.
Cron Monitor keeps that record. It shows what ran, what failed and which plugin is behind each
job, and it tells you when something goes wrong.
wp cronmon runs: recorded runs. Filters: --hook, --status, --since, --limit. Thewp cronmon health: the Cron Health findings. Exits non-zero when one is critical.wp cronmon orphans: every event with its safe-to-delete verdict. --verdict shows only oneactive, unknown, cron-only, orphaned, paused or excluded. Any other value isAll three accept --format=json.
Both routes require manage_options. Use Application Passwords over HTTPS.
GET /wp-json/cronmon/v1/health: the Cron Health findings, a critical count and an okGET /wp-json/cronmon/v1/runs?status=fatal&since=-1%20hour&limit=20: recorded runs. TimestampsInside a cron callback, attach a note to the current run:
do_action( 'cronmon_log', 'reindexed 412 products' );
With Cron Monitor inactive, the call does nothing.
Add to wp-config.php:
define( 'DISABLE_WP_CRON', true );
Then add a system cron entry, every five minutes:
*/5 * * * * cd /path/to/wordpress && wp cron event run --due-now > /dev/null 2>&1
Or, without WP-CLI:
*/5 * * * * wget -q -O - https://example.com/wp-cron.php?doing_wp_cron > /dev/null 2>&1
Cron Monitor never writes to wp-config.php.
Two database tables per site:
cronmon_runs: one row per run. Hook name, an md5 hash of the arguments (never the values),cronmon_log, its notes are stored on the run too: up to 50 notes of 500cronmon_hooks: one row per scheduled event, with the callbacks last seen on it and who ownsOptions, in the WordPress options table:
cronmon_settings: your settings, including the alert email address and webhook URL.cronmon_recording_enabled: whether run history is switched on.cronmon_paused: the jobs you have paused.cronmon_schedules: your custom schedules.cronmon_blocked: the last 20 attempts the duplicate guard refused.cronmon_changelog: the jobs that appeared or disappeared recently.cronmon_alert_item_*: one row for each alert waiting to be delivered, at most 200, each droppedcronmon_alert_queue is the older single-row version of this queue and onlycronmon_overdue_next_check: when the stopped-running check may next run.cronmon_webhook_next_attempt: when the alert webhook may next be tried. After a webhook requestcronmon_db_version: the database version of the two tables.Transients (short-lived cache entries):
cronmon_alerted_*: one per job that raised an alert, so the same job is not alerted againcronmon_overdue_seen: the overdue job seen by the stopped-running check.cronmon_spawn_status: the result of the wp-cron.php check, cached for an hour.cronmon_critical_findings: the count shown in the menu badge, cached for an hour.cronmon_event_form_<user id>: the values you typed into the Add event form if it was refused,cronmon_request_error_<user id>: an error message to show you once, kept for 1 minute.cronmon_install_retry: set for 5 minutes after a failed table install, so the install is not retried on every request.By default, successful runs are kept for 7 days and failures for 14, capped at 50,000 rows. You
can change all three under Tools Cron Monitor Settings. No IP addresses,
user names or visitor data are stored. The only user information is your own user ID in the names
of the last two transients, and the alert email address you enter yourself.
Everything above is removed on uninstall. The one exception is a cronmon_alerted_* transient on a
site with a persistent object cache, which cannot be found by name and expires on its own within
your throttle period.
No third-party libraries are bundled and nothing is minified.
This plugin contacts no third-party service of its own. No analytics, no update checker. It makes
at most two kinds of outbound request, both under your control:
event (fatal, drift or overdue), hookargs_hash (an md5 hash, never the arguments), site (your site’s homeurl (a link to Run History in your WordPress admin), started_at, duration (null for drift and overdue alerts), andtext and content (the same one-sentence summary, which includes your site’s hometext and Discord reads content). Depending on the event it also has errorcount (how many jobs are overdue), late_by, gapexpected (seconds). Your site’s home URL is therefore sent to the service you chose. Termswp-cron.php whether it answers. This goes to your own site_url(). It never runs duringDISABLE_WP_CRON, ALTERNATE_WP_CRON).Alert emails are sent through wp_mail() to the address you enter, using your site’s own mail
setup.