Cronheart
WP-Cron stopped and nothing told you? Cronheart alerts you when scheduled jobs stop running or fail.
Choix solide
Cronheart is a solid plugin choice in 2026, with a few things worth checking first. Was last updated 6 days ago, and scores 64/100 on our health check.
- Développé activement — Dernière mise à jour il y a 6 jours
- Testé avec le dernier WordPress (7.1)
- Petite base d'utilisateurs (<10 installations actives)
- Très peu de critiques jusqu'à présent
- Nécessite PHP 8.2 ou plus récent
Comment s'accumule-t-il ?
Côte à côte sur les installations, les mises à jour, les évaluations et le supportTéléchargements quotidiens
Les pics de téléchargement suivent généralement une nouvelle version - chaque site qui met à jour automatiquement compte comme un téléchargement.
Classements
Where Cronheart stands todayWordPress.org Classements de recherche
Position en direct dans la recherche de plugins, Top 100| Mot-clé | Position |
|---|---|
| cron | >100 |
| deadman-switch | #1 |
| vérification de la santé | #7 |
| monitoring | >100 |
| wp cron | >100 |
About Cronheart
From the official readme · v0.6.0Description
WP-Cron stopped and nothing told you. WordPress runs its scheduled jobs only when someone visits the site. On a quiet site, a backup, a newsletter or a cleanup can stay stalled for weeks before anyone notices. Uptime monitors do not catch it: the site answers over HTTPS just fine, it simply is not running its jobs.
Cronheart turns WP-Cron into a dead-man switch. The plugin pings cronheart.com every five minutes, and sends a start, success or fail ping around every run of each event you register. If the pings stop, or a job fails, cronheart alerts you by email, Telegram, Slack, Discord, Microsoft Teams, Google Chat, PagerDuty or a signed webhook.
Setup in 4 steps
- Installez et activez le plugin.
- Create a free account at cronheart.com.
- Add a monitor for your site that expects a ping every 5 minutes, and copy its UUID.
- Paste the UUID under Settings → Cronheart and save. The first heartbeat is sent on the next WP-Cron run.
Step by step: Monitor WordPress cron with Cronheart.
Ce qu'il fait
- 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 tailingdebug.log. This holds for runs through a page request,wp-cron.php,ALTERNATE_WP_CRONand WP-CLI’swp cron event run. - 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).
- Monitor picker. Save a cronheart.com API token and the site heartbeat field becomes a dropdown of your account’s monitors instead of a hand-typed UUID. Entirely optional — without a token you paste the UUID as before, and any API hiccup falls back to that field. The token is write-only and never leaves wp-admin.
- Account overview and monitor management. With a token configured, Settings → Cronheart shows your plan and monitor budget, and a “Your monitors” table listing each monitor with its status and any active snooze. From that table you can pause, resume, snooze (1 hour, 4 hours, 1 day, or 1 week), or unsnooze a monitor; the change applies on cronheart.com immediately. Every action is an authenticated administrator request — nothing happens without your click.
- Per-event monitoring UI. A Settings → Cronheart Events screen lists the recurring WP-Cron events on your site and lets you, per event, either assign one of your monitors from a dropdown or auto-create an interval monitor for it in one click — no code required. This is the point-and-click alternative to the
cronheart_monitor()helper andCRONHEART_EVENT_<HOOK>_UUIDconstants, which still work. A constant overrides an assignment made on this screen; an assignment made on this screen overrides the helper. - Channel management. A Settings → Cronheart Channels screen lists your cronheart.com notification channels and lets you, per channel, send a real test alert through it or — for webhook channels — rotate the signing secret (revealed once). Creating channels stays on cronheart.com; this screen tests and maintains the ones you already have.
- Ping & alert history. A Settings → Cronheart History screen shows the most recent pings (kind, time, runtime) and alerts (kind, time, channels notified) for a monitor you pick (the picker lists up to 200 monitors) — a read-only at-a-glance log without leaving WordPress.
- Configuration through
wp-config.phpconstants for production (CRONHEART_HEARTBEAT_UUID,CRONHEART_EVENT_<HOOK>_UUID), with admin-UI fallback for sites where editingwp-config.phpis not practical.
Obligations
- WordPress 6.0 or later.
- PHP 8.2 or later with the cURL extension (
curl), which most hosts enable. - A cronheart.com account; the free plan is enough. An API token is optional.
Never breaks WP-Cron
The plugin’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; with WP_DEBUG and WP_DEBUG_LOG on, a ping that fails leaves one line in the debug log. A third-party filter that throws while the plugin reads its settings is caught too. If cronheart goes down for a day, your wp_schedule_event callbacks still run normally; you just stop seeing pings on the dashboard. When the plugin cannot send pings safely (the PHP cURL extension is missing, or the endpoint setting is one it does not accept), it sends none and shows an error notice in wp-admin instead.
Services externes
This plugin sends HTTP requests to cronheart.com in two distinct situations: the monitoring pings your scheduled jobs send, and the account-management calls the admin settings page makes. Both are opt-in: without configuration the plugin loads and does nothing — no telemetry, no usage statistics, no anonymous reports.
1. Monitoring pings (front end / WP-Cron). Sent on every scheduled WP-Cron run, but only when you supply a monitor UUID. The exact data sent per ping:
- The per-monitor UUID you configured (path segment).
- A short body — capped at 10 KB — that is empty for
start/success/heartbeatpings. For afailping it holds the PHP error type, the file path and line, and the message of the fatal error or uncaught exception, or a one-line note that the event did not complete. - The bundled SDK’s name and version in a
User-Agentheader (for examplecron-monitor-php-sdk/1.9).
2. Account management (wp-admin only). When — and only when — you save a cronheart.com API token, the Cronheart admin screens (Settings → Cronheart, Settings → Cronheart Events, Settings → Cronheart Channels, and Settings → Cronheart History) talk to the cronheart.com management API at https://cronheart.com/api/v1/.... Every such request carries the token as an Authorization: Bearer header and runs only while a logged-in administrator is on one of those screens — and, for the write actions below, only when that administrator clicks the control. Never on the front end, during WP-Cron, or in any other context. No token, no request. The calls are:
- Read your monitors —
GET /api/v1/monitors— to populate the heartbeat picker, the “Your monitors” table, the per-event assignment dropdowns, and the Cronheart History monitor picker. Sends nothing beyond the token and paging parameters. - Read your account —
GET /api/v1/account— to show your plan, monitor budget, and API rate-limit standing. Sends nothing beyond the token. - Lifecycle actions —
POST /api/v1/monitors/<uuid>/pause(or/resume,/snooze,/unsnooze) — sent when you click a pause / resume / snooze / unsnooze button. Sends the monitor’s UUID (in the path) and the action; snooze also sends the chosen duration (1 hour, 4 hours, 1 day, or 1 week). - Create a monitor —
POST /api/v1/monitors— sent when you click “Auto-create & assign” for a recurring event on the Cronheart Events screen. Sends the event’s hook name (as the monitor name), its schedule as an interval in seconds, the site timezone, and a grace period — all derived from the WP-Cron schedule — plus an idempotency key that is a SHA-256 hash of the site URL and the hook name (the URL itself is not sent), so a repeated click does not create a second monitor. - Read your channels —
GET /api/v1/channels— to populate the Cronheart Channels screen. Sends nothing beyond the token. - Send a test alert —
POST /api/v1/channels/<id>/test— sent when you click “Send test” on a channel. This delivers a real notification to that channel’s destination (your configured email, Telegram, Slack, Discord, Microsoft Teams, Google Chat, PagerDuty, or webhook), so it is the one management call with an effect outside cronheart.com. Sends only the channel id (in the path). - Rotate a webhook secret —
POST /api/v1/channels/<id>/rotate-secret— sent when you click “Rotate secret” on a webhook channel. cronheart.com mints a new signing secret (shown to you once) and invalidates the previous one. Sends only the channel id (in the path); the new secret is shown in the page and never stored by the plugin. - Read ping & alert history —
GET /api/v1/monitors/<uuid>/pingsandGET /api/v1/monitors/<uuid>/alerts— to populate the Cronheart History screen for the monitor you select. Reads the most recent page only. Sends the monitor’s UUID (in the path) and paging parameters.
The lifecycle, create, test, and rotate-secret calls are the only requests that change anything — and “Send test” additionally delivers a real notification to the channel’s destination, while “Rotate secret” invalidates the old webhook secret — but each is one deliberate administrator click. The token is optional: without it the plugin makes none of these management calls — you assign monitors by hand (or via the constants / helper) and only the monitoring pings above are ever sent.
Cronheart.com Terms of Service · Privacy policy
Open source
Source code and issue tracker: github.com/alexander-po/cronheart-wp.
The plugin wraps the cron-monitor/php-sdk PHP package (also open source, MIT-licensed). Both projects are maintained independently.
Installation
The plugin needs PHP 8.2 or later with the cURL extension (curl), which most hosts enable. Without the extension the plugin sends no pings and shows an error notice in wp-admin.
- Install the plugin: WP Admin → Plugins → Add New → search for “Cronheart” → Install Now → Activate. Or upload
cronheart.zipfrom a GitHub release. - Sign up at cronheart.com and create a monitor for your site’s heartbeat, with a 5-minute schedule. Copy the monitor UUID from the dashboard. Until a UUID is set, a notice on the Plugins screen and the Dashboard links to the setup; you can dismiss it.
- Configure the UUID. Either add it to
wp-config.phpwithdefine( 'CRONHEART_HEARTBEAT_UUID', 'xxxxxxxx-…' );(recommended), or paste it under Settings → Cronheart in the WP admin. - Done. If you saved the UUID under Settings, saving queues one heartbeat for the next WP-Cron run, so the first
heartbeatping shows on the cronheart dashboard shortly after. With thewp-config.phpconstant, the first ping arrives within five minutes. From then on it repeats every five minutes. - (Optional) To choose a monitor from a dropdown instead of pasting its UUID, create a Personal Access Token at cronheart.com (Account → API tokens) and save it under Settings → Cronheart. Every plan, the free one included, can use the API; the account email must be verified before a token can be created. The plugin works fully without a token. For production, prefer
define( 'CRONHEART_API_TOKEN', 'cmk_…' );inwp-config.phpto keep the account credential out of the database.
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.
Journal de modifications
Adds a dismissible setup notice and a Settings link, and queues a first heartbeat when you save a monitor UUID. No settings change; the ping path is unchanged.
0.6.0
- A setup notice on the Plugins and Dashboard screens until a heartbeat UUID is set; each user can dismiss it.
- A Settings link on the plugin’s row in the Plugins list, and first-run steps on Settings → Cronheart.
- Saving a new heartbeat UUID queues one heartbeat for the next WP-Cron run, so the first ping does not wait for the five-minute tick.
- Links to the cronheart.com signup and guide carry a
ref=wp-pluginlabel. - Readme rewritten: shorter description, four-step setup, a fuller FAQ, refreshed screenshots.
0.5.7
- A third-party cron filter that throws no longer stops
wp plugin activateordeactivate, and no longer leaves a wrongcurrent_action()for a monitored event’s own callbacks.
0.5.6
- A server without the PHP cURL extension no longer gets a fatal error on every request. The plugin then sends no pings and shows an error notice in wp-admin to users who can manage options.
- An endpoint setting the plugin rejects (no
http://orhttps://scheme, or plainhttp://withoutCRONHEART_ALLOW_INSECURE_ENDPOINT) now stops all pings and shows an error notice in wp-admin naming the constant or option that holds it. Before, the pings and the monitor UUIDs in them went to cronheart.com instead of the configured host. - A third-party filter that throws while the plugin reads its monitor settings no longer stops a monitored WP-Cron event’s own callbacks, ends the rest of the run, or ends every request; the plugin skips the affected ping instead.
- The
cronheart_allow_insecure_endpointoption now readsfalse,no,offand any unrecognised value as false, like theCRONHEART_ALLOW_INSECURE_ENDPOINTconstant. - With
WP_DEBUGandWP_DEBUG_LOGon, each failed ping writes one line to the debug log, including a ping the service refuses (such as one with a wrong monitor UUID). The line never holds a monitor UUID, an API token or a full URL. - The plugin description is brought up to date: all eight alert channels, what a
failping’s body and theUser-Agentheader contain, the idempotency key of the auto-create call, WP-CLI runs, the retry rules and where to find a monitor’s UUID.
0.5.5
- A monitored WP-Cron event that throws or hits a fatal error now sends its
failping when it is run withwp cron event run(including--due-now), as hosts that drive WP-Cron from a system cron through WP-CLI do. Before, WordPress’s own fatal-error handling ended the WP-CLI process before the plugin could send it, so the monitor received astartand nofailand stayed up. Runs through a page request,wp-cron.phporALTERNATE_WP_CRONalready sent it. Thefailis sent once, and the WP-CLI command’s output and exit code are unchanged.
0.5.4
- A ping that meets a server error or a connection error is now tried up to three times instead of two. After a 503 that carries a whole-second
Retry-Afterthe bundled SDK waits for it; after any other failure it waits a short fixed step; all waits of one ping stay within the ping timeout, and a 4xx answer is not retried. The ping timeout is now 3 seconds per attempt, so one ping takes at most about 12 seconds when the service keeps answering 503 slowly and about 10 seconds when it is unreachable; a ping sent inline in a visitor’s request (ALTERNATE_WP_CRON, or a monitored hook fired by a page request) is held for that time. Requests that use your account API token keep one retry. Bundlescron-monitor/php-sdk1.9. The FAQ answer about a blocked host no longer promises adebug.logline.
0.5.3
- Maintenance release with no change in behaviour. Code comments describe the limits of the cronheart.com monitor API (interval, monitor name length, grace period, channel ids) in the API’s own terms. The development smoke script, which is not part of the plugin package, now fails within seconds on a wrong API token or monitor UUID and waits briefly for the pings to show up.
Captures d'écran
Pour les développeurs
Est-ce votre plugin ? Montrez les chiffres.
Ajoutez un badge en direct à votre site, docs ou github readme. Il se met à jour par lui-même - aucun compte n'est nécessaire.
Best Cronheart alternatives
All cron plugins →FAQ
Cronheart: quick answers
Réponses directes, extraites des données en direct WordPress.org.
Source : WordPress.org
Is Cronheart free?
Yes. Cronheart is free to download and use from the official WordPress.org plugin directory.
Is Cronheart safe to use in 2026?
Cronheart is a solid plugin choice in 2026, with a few things worth checking first. Was last updated 6 days ago, and scores 64/100 on our health check.
How many websites use Cronheart?
Cronheart is active on <10 WordPress websites and has been downloaded 994 times since it launched in May 2026. It was downloaded 404 times in the last 30 days.
Does Cronheart work with WordPress 7.1?
Yes. The developer has tested Cronheart up to WordPress 7.1.5, the latest release. It requires WordPress 6.0 or newer.
What PHP version does Cronheart need?
Cronheart requires PHP 8.2 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Cronheart last updated?
The latest version, 0.6.0, was released on November 13, 2026 (6 days ago).
Who makes Cronheart?
Cronheart is developed and maintained by cronheart.
What are the best alternatives to Cronheart?
The most popular alternatives to Cronheart are WP Crontrol (300K+ installs), Advanced Cron Manager (30K+ installs) and Missed Scheduled Posts Publ… (20K+ installs).
Propulsé par PageForge
Un modèle et une feuille de calcul. Une vraie page pour chaque recherche.
PageForge transforme chaque ligne d'un CSV en une page WordPress avec son propre titre, URL, SEO et schéma, construit sur la mise en page que vous Déjà conçu. Gratuit sur WordPress.org.
- CSV et XLSX, plus Google Sheets sur les professionnels et les entreprises
- Son propre titre, URL, SEO champs et schéma pour chaque page
- Fonctionne avec l'éditeur de blocs, Elementor, Divi et Avada
- Gratuit sur WordPress.org, pas de carte de crédit
