內容簡介
CRX Cron Health Monitor 外掛幫助使用者監控 WordPress 的 WP-Cron 任務，提供詳細的執行數據與問題檢測，確保排程任務正常運行，避免因為隱性錯誤導致的網站功能失效。
【主要功能】
• Cron 健康評分，具體問題明確列出
• 任務歸屬，顯示插件或佈景主題來源
• 實際執行數據，包括執行時間與記憶體使用
• 問題檢測，識別常見的 Cron 問題
• 每個任務的監控與歷史紀錄（付費計畫）
• 隱私保護，無需連接帳號即可使用基本功能
外掛標籤
開發者團隊
原文外掛簡介
Your cron did not fail. It never ran. WP-Cron only fires when someone visits your site. That is why nightly backups silently wait until morning, why DISABLE_WP_CRON without a real cron kills every scheduled task without a word, and why a single fatal error can jam the whole queue while every dashboard stays green.
Cronitorex shows you what is actually happening on your site, and tells you exactly who is responsible.
See your cron for the first time
Cron Health Score (0-100) with named deductions: every lost point is a concrete problem with a concrete fix, never an opaque number
Task attribution: every cron hook mapped to the plugin or theme that registered it, with its version. An alert says “WooCommerce 9.x”, not a cryptic hook name
Real execution data: how long each task took, how late it ran versus its schedule, peak memory, and fatals or timeouts caught mid-task
A task table that answers questions: what runs here, who owns it, when it runs next, how its last run went
Ten detections that name the problem
WP-Cron disabled with nothing triggering it (the most common silent death in WordPress)
Night-time cron gaps: your site sleeps, so your nightly jobs do too
Tasks running long after their scheduled time
Overdue events piling up in the queue
Tasks dying mid-run from fatal errors or PHP timeouts
Orphaned events left behind by removed plugins
Duplicated events doing the same work twice
Tasks slow enough to hurt real visitors
Emails failing to send (wp_mail failures are silent by default)
Mail going through PHP mail() without SMTP, the classic road to the spam folder
Each detection appears in the dashboard with a suggested fix, and in the native Site Health screen (Tools – Site Health), where WordPress admins already look.
The dead man’s switch
Everything above runs locally and needs no account. But a tool that lives inside WordPress has a blind spot it cannot escape: when WP-Cron dies, the tool dies with it. A dead scheduler looks exactly like a healthy one from the inside.
Connecting a free Cronitorex account closes that gap. The plugin sends a heartbeat every five minutes; when your cron stops, the heartbeat stops, and the silence itself raises an alert from outside within minutes. Nothing that runs inside your site can do this.
Per-task monitors (paid plans)
On paid plans, every recurring cron task gets its own monitor with its own history and alerts:
Monitors are created for you, within your plan limit, with alert windows derived from how the task actually behaves (95th percentile of observed runs), not from guesses
Every run reports start, completion or failure, with duration
A task that disappears from the schedule gets its monitor paused, never deleted: destroying history stays a human decision
For developers
WP-CLI: wp cronitorex status, wp cronitorex doctor, wp cronitorex sync
No external libraries, no JavaScript frameworks, no build step
Instrumentation never touches other plugins’ code and never slows a request: all reporting is non-blocking, and every failure of the monitoring itself is swallowed by design
Privacy
The plugin sends nothing anywhere until you connect an account. Once connected, telemetry is aggregate numbers and task names only: run counts, durations, lag. No task arguments, no post content, no emails, no personal data. Ever.
External Services
This plugin can connect to the Cronitorex monitoring service (cronitorex.com). Nothing is sent anywhere until you enter your API keys on the Configuration tab; without keys the plugin is fully local.
Once connected, it talks to two endpoints:
https://api.cronitorex.com – receives monitoring pings: the site heartbeat (aggregate counters: number of runs, failures, worst duration and delay) and, on paid plans with per-task monitors enabled, one ping per task run (task hook name, status, duration). Sent from your server whenever monitored tasks run.
https://app.cronitorex.com/api/v1 – the management API, called only from explicit admin or WP-CLI actions (creating the heartbeat monitor, syncing per-task monitors, reading your plan limits).
Data sent never includes task arguments, post content, emails or personal data.
Service provided by Cronitorex: Terms of Service, Privacy Policy.
