Title: Cronheart Author: cronheart Published: Èbìbí 28, 2026 Last modified: Èbìbí 28, 2026 --- Ṣàwárí àwọn plugin ![](https://ps.w.org/cronheart/assets/banner-772x250.png?rev=3552438) ![](https://ps.w.org/cronheart/assets/icon-256x256.png?rev=3552438) # Cronheart Láti ọwọ́ [cronheart](https://profiles.wordpress.org/cronheart/) [Ṣe ìgbàsílẹ̀](https://downloads.wordpress.org/plugin/cronheart.0.1.9.zip) * [Àwọn àlàyé](https://yor.wordpress.org/plugins/cronheart/#description) * [Àwọn àgbéyẹ̀wò](https://yor.wordpress.org/plugins/cronheart/#reviews) * [Ìgbéwọlẹ̀](https://yor.wordpress.org/plugins/cronheart/#installation) * [Ìdàgbàsókè](https://yor.wordpress.org/plugins/cronheart/#developers) [Ìrànlọ́wọ́](https://wordpress.org/support/plugin/cronheart/) ## Àpèjúwe **WP-Cron is request-driven.** On a low-traffic site no requests arrive, no events fire, and a scheduled backup can be stalled for weeks before anyone notices. Uptime monitors do not catch this — the site responds to HTTPS just fine, it just is not running its jobs. Cronheart turns WP-Cron into a **dead-man switch**: the plugin pings [cronheart.com](https://cronheart.com) every five minutes and on every individual event you register. If the pings stop, cronheart alerts you via email, Telegram, Slack, Discord, or a custom webhook. #### What it does * **Site heartbeat.** A 5-minute custom WP-Cron event whose only job is to ping cronheart. Proves WP-Cron itself is alive on this site. * **Per-event monitoring.** Register any scheduled hook for start / success / fail pings with one PHP one-liner: cronheart_monitor( ‘my_nightly_report’, ‘xxxxxxxx-…’); * **PHP fatal-error capture.** When a scheduled callback fatals or throws, the fail-ping body includes the `error_get_last()` summary — the cronheart dashboard shows the cause without you tailing `debug.log`. * **Settings page.** A read-only “Monitored events” table at Settings Cronheart shows every hook the plugin is watching and where its UUID came from (constant, option, filter). * **Configuration through `wp-config.php` constants** for production (`CRONHEART_HEARTBEAT_UUID`,` CRONHEART_EVENT__UUID`), with admin-UI fallback for sites where editing` wp-config.php` is not practical. #### Never breaks WP-Cron The pluginÌtumọ̀ Yorùbá: ’s hard contract: a broken cronheart backend, an unreachable network, a misbehaving PSR-18 HTTP client — none of them may cause WP-Cron to fail. Every network / HTTP error is swallowed into a logged warning. If cronheart goes down for a day, your `wp_schedule_event` callbacks still run normally; you just stop seeing pings on the dashboard. #### External services This plugin sends HTTP requests to [cronheart.com](https://cronheart.com) on every scheduled WP-Cron run, but **only when you supply a monitor UUID. Without configuration the plugin loads and does nothing — no telemetry, no usage statistics, no anonymous reports. The exact data sent per ping: * The per-monitor UUID you configured (path segment). * A short body excerpt — capped at 10 KB — containing either an exception summary( for `fail` pings) or nothing (for `start` / success / `heartbeat`). * The plugin / SDK version in a `User-Agent` header. [Cronheart.com Terms of Service](https://cronheart.com/terms) · [Privacy policy](https://cronheart.com/privacy) #### Open source Source code and issue tracker: [github.com/alexander-po/cronheart-wp](https://github.com/alexander-po/cronheart-wp). The plugin wraps the [`cron-monitor/php-sdk`](https://github.com/alexander-po/cron-monitor-php) PHP package (also open source, MIT-licensed). Both projects are maintained independently. ## Ìgbéwọlẹ̀ 1. Install the plugin: **WP Admin Plugins Add New ** search for “Cronheart” ** Install Now Activate.** Or upload cronheart.zip from a GitHub release. 2. Sign up at [cronheart.com](https://cronheart.com) and create a monitor for your siteÌtumọ̀ Yorùbá: ’s heartbeat. Copy the monitor UUID from the dashboard. 3. Configure the UUID. Either: 4. * **Recommended:** add to `wp-config.php`: define( ‘CRONHEART_HEARTBEAT_UUID’,‘ xxxxxxxx-…’ ); * **Or:** paste the UUID under **Settings Cronheart** in the WP admin. 5. Done. Within five minutes you should see the first `heartbeat` ping on the cronheart dashboard. For per-event monitoring (a specific scheduled hook, not just the site heartbeat), register the hook from a plugin / theme / mu-plugin: ``` add_action( 'plugins_loaded', function () { cronheart_monitor( 'my_nightly_report', 'xxxxxxxx-…' ); }, 1 ); ``` The hook then emits `start` / `success` (or `fail` on a fatal / thrown exception) pings on every scheduled run. ## FAQ ### Does this work when WP-Cron is disabled (system-cron mode)? Yes. If you set `define( 'DISABLE_WP_CRON', true );` and trigger wp-cron.php from a real system cron, the pluginÌtumọ̀ Yorùbá: ’s heartbeat_tick action still fires on each run — the trigger mechanism is different, the action chain is the same. ### What if my host blocks outgoing HTTPS? The plugin will retry once (built-in retry budget) and then log a warning to `debug. log`. Your scheduled callbacks still run normally — the plugin never raises an exception that could break the cron runner. To diagnose, check `wp-content/debug.log` for entries beginning with “cron-monitor”. ### Do I need a paid cronheart.com account? No. CronheartÌtumọ̀ Yorùbá: ’s free tier covers 20 monitors per account — enough for a typical siteÌtumọ̀ Yorùbá: ’s heartbeat plus several per-event monitors. Paid tiers (Starter / Growth / Scale) raise the cap and unlock additional notification channels. ### Where do I find my monitor UUID? Sign in at [cronheart.com](https://cronheart.com), open the monitor you created, and copy the UUID from the address bar or the “Ping URL” block on the monitor page. ### What happens to my scheduled jobs if cronheart.com is unreachable? Nothing. The plugin catches every network / HTTP error from the SDK and logs a warning — your `wp_schedule_event` callbacks continue to run. You will stop seeing pings on the cronheart dashboard, and after the configured grace period cronheart sends you the down-alert. When cronheart comes back the next successful ping resolves the incident automatically. ### Does the plugin track or report anything about my site? No. The plugin sends a ping to cronheart only when you have configured a monitor UUID. The ping payload is the UUID, an optional short body excerpt (capped at 10 KB), and the SDKÌtumọ̀ Yorùbá: ’s `User-Agent` header. There is no anonymous-statistics beacon, no plugin-usage telemetry, no calls to any third-party analytics service. ### Can I point the plugin at a non-production cronheart deployment (staging / private / self-hosted)? = Yes. Define `CRONHEART_ENDPOINT` in `wp-config.php` with the URL of your alternate deployment. For plain `http://` endpoints (local development, private VPNs without TLS) also set CRONHEART_ALLOW_INSECURE_ENDPOINT to `true`. With both unset, the plugin pings the production cronheart.com over HTTPS. ### Where can I report bugs or request features? Open an issue on [GitHub](https://github.com/alexander-po/cronheart-wp/issues). ## Àwọn àgbéyẹ̀wò Kò sí àwọn àgbéyẹ̀wò fún plugin yìí. ## Àwọn Olùkópa & Olùgbéejáde “Cronheart” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí. Àwọn Olùkópa * [ cronheart ](https://profiles.wordpress.org/cronheart/) [Túmọ̀ “Cronheart” sí èdè rẹ.](https://translate.wordpress.org/projects/wp-plugins/cronheart) ### Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè? [Ṣàwárí koodu](https://plugins.trac.wordpress.org/browser/cronheart/), ṣàyẹ̀wò [ibi ìpamọ́ SVN](https://plugins.svn.wordpress.org/cronheart/), tàbí ṣe àgbékalẹ̀ sí [àkọsílẹ̀ ìdàgbàsókè](https://plugins.trac.wordpress.org/log/cronheart/) nípasẹ̀ [RSS](https://plugins.trac.wordpress.org/log/cronheart/?limit=100&mode=stop_on_copy&format=rss). ## Àkọsílẹ̀ àwọn àyípadà #### 0.1.9 * Plugin Directory review round 2 fix. `Contributors:` changed from `cronmonitor` to `cronheart` — the reviewerÌtumọ̀ Yorùbá: ’s static analysis pointed out that the WordPress.org account that actually owns the `cronheart` plugin slug (and uploaded every version including v0.1.8) is `cronheart`, not cronmonitor. v0.1.7Ìtumọ̀ Yorùbá: ’s switch to `cronmonitor` was a wrong guess at the right owner identity; v0.1.9 puts the actual slug owner in the contributors line. * No code changes. #### 0.1.8 * Bump “Tested up to” from 6.9 to 7.0. The v0.1.7 re-upload was rejected by WP. orgÌtumọ̀ Yorùbá: ’s automated scan because WordPress 7.0 had shipped between our v0.1.5 submission and the v0.1.7 re-upload, and the “Tested up to” header now lagged again. Devstack also moved to `wordpress:7.0-php8.2-apache`; smoke run + Plugin Check re-verified green on 7.0. * No code changes. #### 0.1.7 * Restored Terms of Service / Privacy policy links in the readme. The URLs the WP.org reviewer flagged as HTTP 404 in v0.1.5 (`cronheart.com/legal/terms`, ` cronheart.com/legal/privacy`) were wrong paths — the live pages have always been at cronheart.com/terms and `cronheart.com/privacy`. v0.1.6 removed the links entirely as the most cautious response to the review feedback; v0.1.7 puts them back, pointing at the correct URLs (both return HTTP 200). * No code changes. #### 0.1.6 * Plugin Directory review round 1 fixes. No behaviour changes — pings, hooks, admin UI all identical to 0.1.5. * Removed two `cronheart.com/legal/*` links from the readme that responded with HTTP 404. The “External services” section in this readme already provides a full data-flow disclosure; stand-alone Terms / Privacy pages will be linked back when the corresponding cronheart.com URLs are live. * `Contributors:` set to `cronmonitor` (the WordPress.org account that submitted the plugin); previously held a stale GitHub handle (`alexanderpo`) that did not match any WP.org user. * Release zip no longer ships `vendor/bin/cron-monitor` or vendor/cron-monitor/ php-sdk/bin/cron-monitor — those CLI binaries are part of the SDKÌtumọ̀ Yorùbá:’ s local-dev tooling and have no use inside a WordPress plugin. `bin/build-release. sh` now strips every `vendor/*/bin/` directory at zip time. PSR-4 autoload of the SDKÌtumọ̀ Yorùbá: ’s runtime classes is unaffected. #### 0.1.5 * Bump “Tested up to” from 6.7 to 6.9. WordPress.orgÌtumọ̀ Yorùbá: ’s automated scan blocks submission when the readmeÌtumọ̀ Yorùbá: ’s “Tested up to” lags the current stable WordPress release, even when the underlying code is unchanged — the field is treated as a freshness signal for the Plugin Directory search. Devstack also moved to wordpress:6.9-php8.2-apache; smoke run + Plugin Check re-verified green on 6.9. * No code changes. #### 0.1.4 * Pre-submission cleanup before the WordPress.org Plugin Directory review. No behaviour changes — pings, hooks, and admin UI all identical to 0.1.3. * Release zip no longer ships `CLAUDE.md` and similar contributor-only docs from vendored packages; the bundled tree is now scoped to what the runtime actually needs. * `LICENSE` gained an explicit project copyright header (`cronheart-wp — Copyright( C) 2026 Alexander Palazok`); the GPL-2.0 preamble follows unchanged. * CHANGELOG.md hygiene: missing `[0.1.1]` section header restored; internal sprint- tracking term (“Sprint D”) removed from the public 0.1.3 entry; stale “deferred to v0.1.1+” notes on vendor namespace prefixing rewritten to reflect the current“ deferred pending first reported collision” stance. #### 0.1.3 * WordPress.org Plugin Check fixes: added `defined('ABSPATH')` direct-access guards to every PHP file the static analyser reaches; refactored the monitored-events table render so the escape calls are direct printf arguments (the previous pre- assigned variable was flagged by EscapeOutput); shipped composer.json / `composer. lock` alongside `vendor/` in the release zip so the bundled dependencies are reproducible. * No behaviour changes — pings, hooks, and admin UI all identical to 0.1.2. #### 0.1.2 * WordPress.org submission readiness: full readme.txt (Description, FAQ, Screenshots, External-services disclosure), version bump from 0.1.1. * No code changes — pure metadata polish for the Plugin Directory submission. #### 0.1.1 * Endpoint override: `CRONHEART_ENDPOINT` constant and cronheart_endpoint option for pointing the plugin at a non-production cronheart deployment (staging, private VPC, local backend). * `CRONHEART_ALLOW_INSECURE_ENDPOINT` constant / cronheart_allow_insecure_endpoint option to opt into plain http:// endpoints (required for local backends behind host.docker.internal or TLS-less private VPNs; default false). * Local end-to-end smoke harness under `devstack/` for verifying the plugin against either production cronheart.com (public contributors) or a local cron-monitor backend (maintainers). * No breaking changes — installs without the new constants keep the v0.1.0 behaviour. #### 0.1.0 * Initial scaffold (GitHub-only release; WP.org submission deferred to v0.1.2+). * Site-wide heartbeat layer with a 5-minute custom schedule. * Per-event monitoring with `cronheart_monitor()` helper and cronheart_monitor_map filter. * `CRONHEART_HEARTBEAT_UUID` and `CRONHEART_EVENT__UUID` constants for sourcing UUIDs from `wp-config.php`. * Admin page at Settings Cronheart for sites without wp-config.php access. * PHP fatal-error capture for the fail-ping body. ## Àkójọpọ̀ Meta * Ẹ̀yà **0.1.9** * Ìgbàgbọ́hùn tó kẹ́yìn **ọjọ́ 6 sẹ́yìn** * Àwọn ìgbéwọlẹ̀ tó ṣiṣẹ́ **Tó kéré sí 10** * Ẹ̀yà WordPress ** 6.0 tàbí ju bẹ́ẹ̀ lọ ** * Dánwò dé **7.0** * Ẹ̀yà PHP ** 8.2 tàbí ju bẹ́ẹ̀ lọ ** * Èdè * [English (US)](https://wordpress.org/plugins/cronheart/) * Àwọn àmì * [cron](https://yor.wordpress.org/plugins/tags/cron/)[healthcheck](https://yor.wordpress.org/plugins/tags/healthcheck/) [monitoring](https://yor.wordpress.org/plugins/tags/monitoring/)[wp cron](https://yor.wordpress.org/plugins/tags/wp-cron/) * [Ìwòye Tó Péye](https://yor.wordpress.org/plugins/cronheart/advanced/) ## Àwọn ìbò Kò sí ìwádìí tí a tíì fi ránṣẹ́. [Your review](https://wordpress.org/support/plugin/cronheart/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/cronheart/reviews/) ## Àwọn Olùkópa * [ cronheart ](https://profiles.wordpress.org/cronheart/) ## Ìrànlọ́wọ́ Nǹkan wà tí o fẹ́ sọ? Ṣé o nílò ìrànlọ́wọ́? [Wo àpéjọ ìrànlọ́wọ́](https://wordpress.org/support/plugin/cronheart/)