{"id":11273,"date":"2026-05-28T23:30:04","date_gmt":"2026-05-28T15:30:04","guid":{"rendered":"https:\/\/aeosub.com\/cronheart\/"},"modified":"2026-05-28T23:30:04","modified_gmt":"2026-05-28T15:30:04","slug":"cronheart","status":"publish","type":"post","link":"https:\/\/aeosub.com\/zh\/cronheart\/","title":{"rendered":"Cronheart"},"content":{"rendered":"
\n\n\n\n\n\n\n\n
Developer<\/th>\ncronheart<\/a><\/td>\n<\/tr>\n
Version<\/th>\nv0.1.9<\/td>\n<\/tr>\n
Active Installs<\/th>\n0 +<\/td>\n<\/tr>\n
Requires \/ Tested<\/th>\n6.0 \/ 7.0<\/td>\n<\/tr>\n
Last Updated<\/th>\n2026-05-28 3:27pm GMT<\/td>\n<\/tr>\n
Official Link<\/th>\nView Details \u2192<\/a><\/td>\n<\/tr>\n<\/table><\/div>\n
Dead-man-switch monitoring for WP-Cron. Get alerted when scheduled events stop firing \u2014 uptime monitors do not catch this.<\/div>\n

WP-Cron is request-driven.<\/strong> On a low-traffic site no requests
\narrive, no events fire, and a scheduled backup can be stalled for
\nweeks before anyone notices. Uptime monitors do not catch this \u2014 the
\nsite responds to HTTPS just fine, it just is not running its jobs.<\/p>\n

Cronheart turns WP-Cron into a dead-man switch<\/strong>: the plugin pings
\ncronheart.com<\/a> every five minutes and on
\nevery individual event you register. If the pings stop, cronheart
\nalerts you via email, Telegram, Slack, Discord, or a custom webhook.<\/p>\n

What it does<\/h4>\n