| 开发者 | kstmonowar |
|---|---|
| 更新时间 | 2026年9月23日 11:22 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/ or install from Plugins > Add New.Low traffic, caching, or DISABLE_WP_CRON can stop schedules from firing. Open the Health tab — it shows enabled, reachable, late count and total with Green / Yellow / Red plus fix steps (e.g. set up a real server cron hitting wp-cron.php).
Find the event in Tools > Cron Manager and click Run now. The run is logged in the Log tab with duration.
Yes. Click Pause — the job is kept as a backup and will not run until you Resume it. Core jobs cannot be deleted (blocked with a warning).
No. Admin pages only. No CSS/JS on the frontend.
Core jobs cannot be deleted (blocked with a warning). Custom jobs can be deleted. Pause keeps a backup to resume.
No. Everything stays in wp_options (autoload=no). No remote calls except a loopback check to your own wp-cron.php for the Health tab.
No, and that is intentional for safety and org approval. You can only trigger an existing hook.
Usually low traffic (nothing triggers WP-Cron), a caching layer serving pages without running PHP, or DISABLE_WP_CRON with no server cron replacing it. Open the Health tab — Green / Yellow / Red plus fix steps tell you which one it is.
Define DISABLE_WP_CRON as true in wp-config.php, then add a server cron job that calls wp-cron.php every few minutes (your host's control panel usually has a Cron Jobs screen). ScheduleLens keeps working — its Health tab will show the system cron driving schedules.
WP-Cron only runs when someone visits your site; on a quiet site, scheduled jobs fire late or never. A system cron runs on the clock regardless of traffic. That is the whole difference, and the reason quiet sites miss schedules.
The Source column on the events list names the plugin (or theme, or WordPress core) that registered each job. An unknown source usually means custom code in functions.php or a must-use plugin.