What is WP Crontrol plugin?
WP Crontrol is a WordPress plugin for viewing, editing, adding, and deleting WP-Cron events directly from the WordPress admin. WordPress’s WP-Cron is a pseudo-cron system that fires scheduled events on page load rather than on a true server-side schedule. Many plugins rely on WP-Cron for background tasks — backup scheduling, email delivery, cache purging, data import, and analytics processing. When these tasks fail silently, WP Crontrol provides the visibility to diagnose what is (or is not) running.
WP Crontrol displays all scheduled cron events with their next run time, the recurrence interval, and the action hook name. Overdue events (past their scheduled execution time) are highlighted in red — a common signal of WP-Cron problems caused by low-traffic sites where pages are not loaded frequently enough to trigger the cron system. The plugin allows manually running any scheduled event immediately (bypassing the schedule), editing event timing, and adding custom PHP cron events for testing or administrative purposes.
WP Crontrol also provides a Cron Schedules screen where custom recurrence intervals registered by plugins can be viewed and added. This is particularly useful for auditing which plugins are using cron extensively — a plugin adding a cron event on every page load (a common bug) will appear as a rapidly accumulating entry in WP Crontrol’s events list. The plugin is entirely free and is an essential diagnostic companion to Query Monitor for understanding WordPress’s background task execution.
Need Help With WP Crontrol Setup, Troubleshooting, or Customization?
Need help with WP Crontrol? Whether you are dealing with errors, broken functionality, styling problems, plugin conflicts, or advanced customization, we can help you fix the issue and get the plugin working properly on your WordPress site.
Get WP Crontrol Expert HelpKey Features
- View all scheduled WP-Cron events with next run time, interval, and hook name
- Identify overdue events (highlighted in red)
- Manually trigger any cron event immediately
- Edit event timing and recurrence
- Add custom PHP cron events
Pros & Cons
Pros
- Provides essential visibility into WordPress background task scheduling
- Overdue event highlighting immediately identifies cron problems
- Manual event triggering enables testing scheduled tasks without waiting
Cons
- Cannot fix underlying WP-Cron reliability issues — it diagnoses but does not replace WP-Cron with a real server cron
- Adding PHP cron events via the admin (custom code execution via cron) is a potential security concern on shared hosting
Free vs Premium
Completely free. No paid version.
Common Problems & Fixes
WP Crontrol shows many overdue WP-Cron events — why are they not running and how do I fix this?
WP-Cron only fires when a page is visited on your site. On low-traffic sites or sites with long periods between visits, scheduled events accumulate past their run time. Solutions: (1) replace WordPress default WP-Cron with a true server cron — add define(“DISABLE_WP_CRON”, true) to wp-config.php, then create a server cron job (via hosting control panel) that calls wp-cron.php on a schedule: curl -s https://yourdomain.com/wp-cron.php?doing_wp_cron > /dev/null; (2) use a service like EasyCron or UptimeRobot to ping your site regularly, ensuring WP-Cron fires. After setting up server cron, overdue events process immediately on the next cron run.
A plugin is adding hundreds of duplicate cron events — WP Crontrol shows the same event hook scheduled repeatedly. How do I fix this?
Duplicate cron events occur when a plugin calls wp_schedule_event() on every page load without first checking if the event is already scheduled. This is a plugin bug. Immediate fix: use WP Crontrol to delete the duplicate events (keep one). Long-term fix: contact the plugin developer with a report of the issue — include a screenshot of WP Crontrol showing the duplicates. If the plugin continues adding events on every page load, deactivate it and find an alternative. This bug can cause significant database bloat in wp_options (where cron events are stored) and performance degradation.
A scheduled WP-Cron event appears in WP Crontrol but is not executing — the event time passes but the task does not run. How do I diagnose this?
Use WP Crontrol to manually run the event: click “Run now” next to the event. If running it manually produces an error, the error message reveals the failure cause (PHP function not found, permission error, etc.). Check: (1) the hook callback function exists and is properly registered with add_action($hook, $callback); (2) the plugin registering the hook is still active; (3) the function does not timeout or hit PHP memory limits — add WP_DEBUG to capture errors; (4) the server has internet access if the cron task requires external connections.
Customization & Developer Notes
How do I set up a server-level cron job to replace WordPress's default WP-Cron?
First, disable WordPress’s page-load-triggered cron: add define(“DISABLE_WP_CRON”, true) to wp-config.php. Then create a server cron job using your hosting control panel’s cron scheduler (or Linux crontab). Set the job to run every 5–15 minutes: */5 * * * * curl -s https://yourdomain.com/wp-cron.php?doing_wp_cron > /dev/null 2>&1. Alternatively, use WP-CLI: */5 * * * * cd /path/to/wordpress && wp cron event run –due-now > /dev/null 2>&1. After setup, verify in WP Crontrol that overdue events are no longer accumulating.
How do I add a custom scheduled cron event using WP Crontrol for testing?
Go to Tools → Cron Events → Add Cron Event. Enter a hook name (e.g., my_custom_daily_task), a PHP function to execute (if using the “Cron Event With PHP Code” option — this requires proper function syntax), a next run time, and a recurrence interval. The custom event will be scheduled in WordPress’s cron queue and fire at the specified time. For production cron tasks, register them properly in plugin or theme code using wp_schedule_event() in an activation hook rather than through WP Crontrol’s admin UI.
Frequently Asked Questions
Is it safe to delete cron events using WP Crontrol?
Deleting plugin-registered cron events can affect plugin functionality. For example, deleting a backup plugin’s scheduled backup event prevents backups from running. Deleting events is safe for: clearly duplicate entries of the same event (keep one), test or orphaned events from deactivated plugins, and events from plugins you are intentionally disabling cron functionality for. For events from active plugins, only delete if you understand what the event does and intentionally want to prevent it from running.
Does WP Crontrol work with WordPress Multisite?
WP Crontrol works on individual sites in a WordPress Multisite network — it manages cron events for the currently active site. Each site in the network has its own cron queue. WP Crontrol does not provide a network-wide view of all sites’ cron events from the Network Admin. For network-level cron management, access WP Crontrol on each individual site’s admin.
Can WP Crontrol break after updates?
Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.
What should I check before installing WP Crontrol?
Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.