by snagbane 1 (0 reviews)

Snagbane Cron Monitor

Name: Snagbane Cron Monitor
Author: snagbane

Tells a genuinely stuck WP-Cron apart from a quiet site that simply had no visitors -- instead of crying wolf, or saying nothing at all.

Snagbane Cron Monitor ranks #70,000 among WordPress.org plugins with 1+ active installations, is #3,581 of 5,007 in the Utilities & Tools category, a 1/5 rating from 0 reviews, and was last updated Sep 24, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1

v0.3.0 Current Version v0.3.0

Updated 14 hours ago Last Update on 24 Sep, 2026

Refreshed 11 hours ago Last Refreshed on

#3,581 of 5,007 in Utilities & Tools Actively maintained

View on WordPress.org

Rank

#70,000

— No change

Active Installs

— No change

KW Avg Position

— No change

Downloads

+36 today

Support Resolved

— No change

Rating

20%

Review 1 out of 5

1 (0 reviews)

Next Milestone 10

Total Progress -2045190%

0+ 10+

20,453

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 204,529 more installs to reach 10+

Rank Changes

Current #69,564

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

1.0

0 reviews

Overall 20%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 0.3.0
Last Updated: Sep 24, 2026
Requires WP: N/A+
Tested Up To: 7.1
PHP Version: N/A
Author: snagbane

Support & Rating

Rating: ★ ☆ ☆ ☆ ☆ 1
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

cron cron job missed schedule scheduled posts wp cron

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,760

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

30K+ installs

#1,009

Elementor Website Builder - more than just a page builder

10M+ installs

Contact Form 7

10M+ installs

All-in-One WP Migration and Backup

5M+ installs

#10

UpdraftPlus: WP Backup & Migration Plugin

4M+ installs

#14

WPCode - Insert Headers and Footers + Custom Code Snippets - WordPress Code Manager

View all Utilities-and-tools plugins

Frequently Asked Questions

Common questions about Snagbane Cron Monitor

It will tell you whether the cause is cron. A post scheduled for a time that has passed and never went live means WordPress never got to run its publishing task, and this plugin shows you whether cron has been running at all, when it last ran, and which tasks were missed. If cron is running fine and the post still did not publish, the cause is elsewhere and you have ruled out the most common culprit. Pro goes further and tells you which specific thing is blocking cron.

No, and that is the specific thing this plugin exists to get right. A stale heartbeat is only reported as "Not working" when the site actually had recent visitors and cron still did not run. Otherwise it is reported as "Running late", which is a much less alarming and much more accurate thing to say.

No. It only observes. It never reschedules, disables or modifies another plugin's events. The one thing it schedules is its own five-minute heartbeat, which does nothing except give WP-Cron a predictable reason to tick.

Yes, and it is detected. With that constant set, the verdict switches to checking whether your server cron is actually reaching wp-cron.php, and says so plainly either way instead of reporting the healthiest possible setup as a fault.

Every individually scheduled task this plugin watched, whether it ran or was missed, with how late it was. Not just the overall heartbeat. Thirty days on every install, and the screen shows all of it.

No. Naming the plugin or theme responsible is a Pro feature. The free log shows that a task ran or was missed, and when.

No. A front-end page view reads one option and, at most once a minute, writes it back. Everything else happens inside the WP-Cron request, which is a background request already.