Harvify Cron Monitor shows you exactly what your site's scheduler is doing \u2014 and tells you when it stops. Unlike basic cron viewers, it records an execution history (duration, memory, success\/error) so you can see what actually ran, not just what is scheduled.<\/p>\n\n
Free features:<\/strong><\/p>\n\n Pro features.<\/strong> These are not part of this plugin and are not included in this\ndownload. They are provided by a separate plugin distributed by Harvify:<\/p>\n\n Action Scheduler events are measured precisely (we hook its before\/after execution events). WordPress core has no native per-event start\/finish hook, so WP-Cron timings are best-effort<\/strong>: we bracket each due hook's callback on the cron request and record a fatal\/timeout via the shutdown handler. WP-Cron rows are labelled \"approx.\" in the history so you always know which numbers are exact.<\/p>\n\n This plugin does not evaluate code. It schedules hooks that already exist on your site, and can optionally perform an HTTP request on a schedule. There is no code editor and no author-supplied code is ever stored or executed.<\/p>\n\n This plugin connects to Freemius, the licensing and update service Harvify uses to\nsell and deliver the Pro tier of its plugins.<\/p>\n\n Nothing is sent to Freemius unless you choose to send it. On activation you are shown\nFreemius's standard opt-in screen. Until you answer it a fresh install makes no\noutbound request at all, and if you choose Skip the free tier stays fully usable\nand still sends nothing. Data is transmitted only when you take one of these\nactions:<\/p>\n\n Service provided by Freemius, Inc. - https:\/\/freemius.com\/\nTerms of service: https:\/\/freemius.com\/terms\/\nPrivacy policy: https:\/\/freemius.com\/privacy\/<\/p>\n\n Cron Monitor can run a \"URL event\": a scheduled request to an address you supply. No\nURL event exists until an administrator creates one, and there is no default\ndestination, so a fresh install contacts nothing. An administrator can also switch\nURL events off entirely in Settings, which stops any that already exist from running.<\/p>\n\n Sent: an HTTP GET to the URL you entered. The plugin adds no page content and no\ninformation about your users. As with every HTTP request WordPress makes, the\nstandard request header identifies the sender as \"WordPress\/; \", so the destination you chose can see your site address.<\/p>\n\n\n No. It monitors and manages the existing WP-Cron system and, when present, Action Scheduler. It does not change how cron is triggered.<\/p><\/dd>\n WordPress core does not expose a per-event start\/finish hook, so WP-Cron timings are best-effort. Action Scheduler jobs are measured exactly.<\/p><\/dd>\n No. It schedules hooks that already exist on your site and can make scheduled HTTP requests. It contains no code editor and no evaluator.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
\n
A note on timing accuracy<\/h3>\n\n
Security<\/h3>\n\n
\n
manage_options<\/code> capability and a valid nonce.<\/li>\nExternal services<\/h3>\n\n
\n
URL cron events (optional, no default destination)<\/h4>\n\n
\n
\/wp-content\/plugins\/harvify-cron-monitor\/<\/code><\/li>\n\n
Does this replace WP-Cron?<\/h3><\/dt>\n
Why are some durations marked \"approx.\"?<\/h3><\/dt>\n
Does this plugin run custom PHP?<\/h3><\/dt>\n
1.0.21<\/h4>\n\n
\n
anonymous_mode<\/code> option, so activation now shows Freemius's\nstandard opt-in screen. Nothing is sent before you answer it, and choosing Skip\nleaves the free tier fully usable and still sends nothing.<\/li>\n1.0.18<\/h4>\n\n
\n
hcm_<\/code> prefix, which is shorter than WordPress.org accepts.\nFunctions, options, cron hooks and the plugin's own actions and filters are now\n harvify_cron_*; global constants are HARVIFY_CRON_*<\/code>; classes are\n Harvify_Cron_*.<\/li>\nharvify-cron\/v1<\/code>. The old hcm\/v1<\/code>\nnamespace is GONE and there is no compatibility alias<\/strong> \u2014 any code that calls\n hcm\/v1 routes will 404 until it is updated. Also renamed: the admin script and\nstyle handle hcm-admin<\/code> is now harvify-cron-admin<\/code>, the localized JavaScript\nobject hcmAdmin<\/code> is now harvifyCronAdmin<\/code>, and the plugin's hooks are now\n harvify_cron_run_recorded, harvify_cron_digest_frequency_changed<\/code> and\n harvify_cron_fs_loaded.<\/li>\n1.0.15<\/h4>\n\n
\n
1.0.14<\/h4>\n\n
\n
Contributors<\/code> field now names the correct WordPress.org account.<\/li>\n1.0.13<\/h4>\n\n
\n
1.0.12<\/h4>\n\n
\n
1.0.11<\/h4>\n\n
\n
1.0.10<\/h4>\n\n
\n
admin-ui<\/code>, so the package shipped in the download but was never loaded and\nthe control could not render -- which also meant the opt-in could never be switched on. Fixed by\nloading the package. Your data was never at risk: with the control unreachable the plugin always\ntook the safe path and kept everything.<\/li>\n<\/ul>\n\n1.0.9<\/h4>\n\n
\n
1.0.8<\/h4>\n\n
\n
1.0.7<\/h4>\n\n
\n
1.0.6<\/h4>\n\n
\n
1.0.5<\/h4>\n\n
\n
1.0.4<\/h4>\n\n
\n
1.0.3<\/h4>\n\n
\n
1.0.2<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n