Understanding wp cron wordpress is essential for reliable background work like scheduled posts, subscription renewals, product syncs, and email sends. This expanded guide teaches how WP‑Cron operates, shows step‑by‑step implementation choices, provides practical examples and trade‑offs, and covers troubleshooting and safety cautions so you can run scheduled tasks predictably.
How WP‑Cron Works (Recap)
WP‑Cron is a pseudo‑cron implemented inside WordPress. The system stores scheduled events in the database and checks for due events on each page load. If a job is due, WordPress attempts to execute it during that request. This design makes scheduling portable and host‑friendly, but it ties reliability to site traffic, request routing, and PHP execution availability.
Official docs: WordPress Cron API and WordPress Cron.
When to Use System Cron Instead
Consider switching to a system cron when you need precision, reliability, or you run critical commerce workflows. Use system cron for:
- Low or highly variable traffic sites where WP‑Cron delays or misses events.
- Time‑sensitive tasks such as payment retries, subscription renewals, inventory syncs, or time‑limited promotions.
- Environments with aggressive caching, reverse proxies, or firewalls that block asynchronous requests.
Implementation Steps
- Audit Current Scheduled Events: Install WP Crontrol (WP Crontrol) on a staging site to list hooks, schedules, recurrence, and next run times. Export or screenshot the list before changes.
- Choose Strategy: Decide between leaving WP‑Cron enabled (convenient) or disabling it and using a system cron (reliable). Document the decision and reasons in your runbook.
- Disable WP‑Cron Safely: If using system cron, add the following to wp‑config.php on staging/test first and then production after backup: define(‘DISABLE_WP_CRON’, true); Keep backups and note the file change in version control or deployment notes.
-
Create a System Cron Job: On a Linux host, create a crontab entry to call the WP cron runner every 5–15 minutes. Example cron entry to run every 5 minutes (adjust to host rules and load):
*/5 * * * * curl -fsS –compressed “https://example.com/wp-cron.php?doing_wp_cron” >/dev/null 2>&1
Schedule frequency based on business needs: heavy commerce sites may need 1–5 minutes, smaller sites 10–15 minutes. Coordinate with managed hosting support when server access is restricted.
- Use Secure Access: Prefer HTTPS calls and, where supported, use a server‑side HTTP client (curl or wget). Some hosts support wp‑cli cron: wp cron event run –due-now as a non‑HTTP alternative that avoids web routing and caching layers.
- Batch and Queue Jobs: For large imports or thousands of products, break jobs into small batches (e.g., 50–200 items per run) and use transients or database flags to track progress. Consider WP‑CLI or Action Scheduler for heavy workloads.
- Monitor and Alert: Log outcomes, check for errors, and set alerts for missed runs or repeated failures. Use simple health checks that inspect scheduled hook statuses or log timestamps to detect stalls.
Practical Examples
- WooCommerce Subscription Renewal: Use system cron to trigger renewals at exact times. Example flow: schedule renewal attempt -> attempt charge via payment gateway -> on success update subscription status -> on failure retry with exponential backoff and notify the admin. Always test with the payment provider sandbox and document provider‑specific retry windows to remain PCI compliant.
- Inventory Sync: For nightly supplier feeds, run a system cron at off‑peak hours. Implement delta processing to only update changed SKUs and use batch commits to avoid long DB locks.
- Large CSV Import: Use WP‑CLI to import in chunks from the shell, or schedule chunked jobs via cron that process N rows per invocation. This reduces PHP memory pressure and avoids web timeouts.
Trade‑Offs
- WP‑Cron: Quick to set up, portable across hosts, no server cron access required. Trade‑offs: runs only on page loads, affected by caching, less predictable for critical jobs.
- System Cron: Precise, reliable, and decoupled from visitor traffic. Trade‑offs: requires server access or host coordination, careful handling of permissions, and additional monitoring.
Troubleshooting: Fix WP Cron Not Working
- No or Low Traffic: Move to system cron or configure a remote uptime monitor to hit a lightweight endpoint to trigger cron if you cannot access server cron.
- Caching/Proxies Blocking Requests: Ensure wp-cron.php and admin-ajax endpoints are excluded from page cache and CDN caching rules. Add cache bypasses for URLs containing doing_wp_cron where applicable.
- Permission/Execution Errors: If your system cron cannot execute, verify file permissions, PHP binary path, user privileges, and SELinux/AppArmor policies. Run the cron command manually to reproduce errors and check web server and PHP logs.
- Fatal Hook Errors: A failing callback will stop an event. Use WP Crontrol to run the hook manually in staging and inspect PHP error logs. Add try/catch and error handling to callbacks to prevent silent failures.
- Database Locking/Overlap: Prevent overlapping runs with transient locks, mutex tables, or use Action Scheduler’s built‑in locking. Long jobs should update progress markers and gracefully exit if another process holds the lock.
Safety, Backups, and Compliance
Always test cron changes in staging and keep full backups before changing scheduling behavior. For comments, forms, and payment‑related cron tasks, emphasize privacy and security: avoid storing sensitive data in plain text, follow payment provider PCI guidance, and restrict log access. Use least‑privilege for cron user accounts and document all commands and schedules so teams can maintain or rollback safely.
Concise Conclusion
Mastering wp cron wordpress means choosing the execution model that fits your traffic and reliability needs, breaking heavy work into safe batches, monitoring runs, and using system cron where precision matters. Follow staging tests, backups, permission reviews, and host‑specific guidance to keep scheduled posts, imports, and commerce processes running predictably and securely.
