Diagnose recovery health and follow guided fixes
Check local capture, your sender and the recovery queue in WordPress. Free needs no account connection.
Review the health screen
- In WordPress, open WooCommerce → WakeMyCart, then select Recovery health. Select Run health check and review each card. Free needs no WakeMyCart account or connection code.
- Expand What to do next for specific actions and a link to the relevant screen or guide.
- Confirm capture with an opted-in test checkout. No recent carts alone does not prove a capture failure.
- Inspect overdue, failed or uncertain jobs. A paused store may intentionally have waiting messages; uncertain provider acceptance must be reconciled before retrying.
- Check your sender’s domain setup and inspect a real inbox. Configure delivery feedback where your provider supports it. WordPress/SMTP handoff and provider acceptance do not prove inbox placement; missing feedback can require a manual review.
Keep recovery running on quiet stores
The local recovery engine schedules work every minute through WooCommerce Action Scheduler. WordPress scheduled tasks must run reliably; page-load scheduling can be delayed on low-traffic stores.
Ask your hosting provider to run WordPress scheduled tasks every minute. Configure and verify that server task before disabling page-load WP-Cron. A disabled WP-Cron flag alone does not prove a server task exists.
Recovery health warns when no successful local run has completed within ten minutes. After fixing the task runner, select Run health check and confirm that the last successful run advances. The check reads local health and refreshes account access only when connected; it does not run the recovery scheduler or enable sending.
Local retention cleanup runs at most hourly in bounded batches. Large backlogs require multiple cleanup runs; confirm that scheduled tasks continue completing.
Health checks and alerts work together
Local Recovery health is available in both editions without an account connection. A connected account can also provide alerts about connection, queue, sending and usage issues. Open Recovery health on the affected store to investigate the alert.
Check the time of the last successful background run and review any delivery warnings about complaints, bounces or missing feedback. Consult the provider before resolving an uncertain message; blindly retrying can send a duplicate.
Include this article and your store’s support summary.