The Pro add-on's "Purchase" buttons on the Add-Ons screen now open the plan you clicked.<\/p>","0.3.0":"
Fixes a fatal error that could stop WP-Cron the first time this plugin caught a missed task, and stops tasks being reported as missed when two cron requests overlap. Multisite networks larger than 100 sites are now set up in full. Updating is strongly recommended.<\/p>","0.2.0":"
Renamed to Snagbane Cron Monitor. History is now a full 30-day log on every install, shown in full, instead of the last five events.<\/p>","0.1.5":"
Adds an optional one-time review prompt after a genuinely caught missed cron. No other behaviour changes.<\/p>","0.1.0":"
First release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3711157,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3711157,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3711157,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3711157,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.3.0","0.3.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3711157,"resolution":"1","location":"assets","locale":"","width":1280,"height":1060},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3711157,"resolution":"2","location":"assets","locale":"","width":587,"height":210}},"screenshots":{"1":"The verdict at a glance, with the history of what ran and what was missed below it.","2":"The dashboard widget: one sentence on whether WP-Cron is doing its job."}},"plugin_section":[262246],"plugin_tags":[4567,4688,69797,25064,4568],"plugin_category":[59],"plugin_contributors":[282127],"plugin_business_model":[],"class_list":["post-374914","plugin","type-plugin","status-publish","hentry","plugin_section-dashboard-widgets","plugin_tags-cron","plugin_tags-cron-job","plugin_tags-missed-schedule","plugin_tags-scheduled-posts","plugin_tags-wp-cron","plugin_category-utilities-and-tools","plugin_contributors-snagbane","plugin_committers-snagbane"],"banners":{"banner":"https:\/\/ps.w.org\/snagbane-cron-monitor\/assets\/banner-772x250.png?rev=3711157","banner_2x":"https:\/\/ps.w.org\/snagbane-cron-monitor\/assets\/banner-1544x500.png?rev=3711157","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/snagbane-cron-monitor\/assets\/icon-128x128.png?rev=3711157","icon_2x":"https:\/\/ps.w.org\/snagbane-cron-monitor\/assets\/icon-256x256.png?rev=3711157","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/snagbane-cron-monitor\/assets\/screenshot-1.png?rev=3711157","caption":"The verdict at a glance, with the history of what ran and what was missed below it."},{"src":"https:\/\/ps.w.org\/snagbane-cron-monitor\/assets\/screenshot-2.png?rev=3711157","caption":"The dashboard widget: one sentence on whether WP-Cron is doing its job."}],"raw_content":"\n
If your scheduled posts are not publishing, your backups stopped running, or a plugin says its task is \"queued\" and never gets further, the usual advice is the same everywhere: check whether WP-Cron is disabled, trigger it by hand, install something that pings it once and calls it a day. None of that answers the actual question, which is whether your scheduled tasks are really not running, or whether your site is simply quiet.<\/p>\n\n
That distinction is the whole problem. WP-Cron is not a real system cron. It only fires when somebody visits the site, so a low-traffic site naturally goes hours between ticks. That is not the same thing as a backup silently failing for a week -- but most cron checkers treat the two identically, and you get either constant false alarms on a quiet site or a real failure nobody notices.<\/p>\n\n
Cron Monitor watches two separate signals instead of one:<\/p>\n\n
Together those tell \"cron is fine, the site is just quiet\" apart from \"cron is genuinely stuck\", and you get one plain sentence rather than a timestamp to interpret:<\/p>\n\n
A site deliberately running a real server crontab with Everything described above is free, on every install, with no cap, no time limit and no nag screens. There is no locked feature anywhere in this plugin.<\/p>\n\n Snagbane Cron Monitor Pro<\/strong> is a separate, optional add-on (not included in this download and not distributed through WordPress.org). It does things this plugin does not do at all:<\/p>\n\n Pro is available from cronmonitor.snagbane.com and requires this free plugin to be installed and active.<\/p>\n\n This plugin connects to one external service:<\/p>\n\n Freemius<\/strong>, our licensing and update platform. The Freemius SDK is used to check for updates, apply the Free\/Pro state, and -- only if you opt in on first activation -- share basic, non-personal usage and site data used to improve the plugin. This connects to freemius.com. No data is sent unless you activate the plugin, and the optional opt-in can be declined without affecting anything. See the Freemius Privacy Policy<\/a> and Terms of Service<\/a>.<\/p>\n\n The plugin makes no other outbound requests. Its detection runs entirely on your own server, observing your own site's existing WP-Cron activity.<\/p>\n\n\n 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.<\/p><\/dd>\n 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.<\/p><\/dd>\n 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.<\/p><\/dd>\n 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.<\/p><\/dd>\n 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.<\/p><\/dd>\n No. Naming the plugin or theme responsible is a Pro feature. The free log shows that a task ran or was missed, and when.<\/p><\/dd>\n 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.<\/p><\/dd>\n\n<\/dl>\n\n\nDISABLE_WP_CRON<\/code> set is recognised as the healthy setup it is, rather than reported as broken because WordPress is not the one spawning the request.<\/p>\n\nWhat you get<\/h4>\n\n
\n
Free vs. Pro<\/h4>\n\n
\n
External Services<\/h3>\n\n
\n
\/wp-content\/plugins\/snagbane-cron-monitor<\/code>.<\/li>\n\n
My scheduled posts are not publishing. Will this tell me why?<\/h3><\/dt>\n
Will this tell me my site is broken just because it is quiet?<\/h3><\/dt>\n
Does this replace WP-Cron, or change how my tasks run?<\/h3><\/dt>\n
I use a real server cron with DISABLE_WP_CRON. Does that work?<\/h3><\/dt>\n
What is in the history log?<\/h3><\/dt>\n
Does the free version name the plugin behind a missed task?<\/h3><\/dt>\n
Does it slow my site down?<\/h3><\/dt>\n
0.3.1<\/h4>\n\n
\n
0.3.0<\/h4>\n\n
\n
get_sites()<\/code> defaults to 100 and has no \"all\" value, so every site past the hundredth silently had no tables and no scheduled events -- and kept its table forever on deletion. Activation now covers 200 sites inline and every site beyond that sets itself up on its first load; deletion pages through the whole network.<\/li>\n0.2.0<\/h4>\n\n
\n
Plugin URI<\/code> header pointed at this plugin's own wordpress.org listing page, which WordPress.org's header requirements disallow. Now points to cronmonitor.snagbane.com.<\/li>\nDescription<\/code> was over WordPress.org's length limit for that field, as was this readme's short description.<\/li>\nLicense<\/code> from GPL-2.0-or-later<\/code> to GPLv2 or later<\/code>, matching WordPress.org's own documented example.<\/li>\n<\/ul>\n\n0.1.5<\/h4>\n\n
\n
0.1.4<\/h4>\n\n
\n
0.1.3<\/h4>\n\n
\n
0.1.2<\/h4>\n\n
\n
0.1.1<\/h4>\n\n
\n
0.1.0<\/h4>\n\n
\n