Performance
wp-cron-action-scheduler-health
Keep WP-Cron and Action Scheduler healthy
Moves scheduled WordPress work to a server cron, diagnoses missed or duplicate jobs, and keeps Action Scheduler queues healthy.
- Area
- Performance
- Checked against
- WordPress 7.1.2, WP-CLI 2.12.0, Action Scheduler 4.0.0 and 4.2.0, WooCommerce 11.1.2
- Last verified
- 26 September 2026
- Files
- SKILL.md, 11 references, 5 scripts
How it works
- 1Record WordPress, WP-Cron, Action Scheduler and runner state with read-only checks.
- 2Find every existing runner and record its interval and user.
- 3Check WP-Cron events for late, failed, duplicate or unusual schedules.
- 4Inspect Action Scheduler queues, failures, claims, runners and retention backlogs.
- 5Match each finding to its confirmed or unconfirmed cause.
- 6Plan and make each approved cron change with its backup, check and undo.
- 7Verify the new runner before tuning queues or cleaning old actions.
Use it when
- Fix missed scheduled posts or late WordPress events.
- Investigate delayed WooCommerce emails, webhooks or renewals.
- Diagnose duplicate scheduled work or growing Action Scheduler tables.
- Move a WordPress site from page-view spawning to server cron.
How it stays safe
- Starts read-only and asks for owner approval before each change.
- Keeps one runner per site and identifies existing runners before adding another.
- Backs up
wp-config.php, the site user's crontab and Action Scheduler tables before relevant changes. - Rehearses schedule changes on staging and runs production changes at a quiet hour.
Install it
Copy the whole wp-cron-action-scheduler-health folder into your agent's skills folder, not only SKILL.md.
git clone --depth 1 https://github.com/hamzaahmadaslam/agent-skills.git
cp -R agent-skills/wp-cron-action-scheduler-health "<your agent's skills folder>/"