WooCommerce Subscriptions: Health Check and processing reliability

Use this when debugging WCS 8.8+ subscription processing, missing renewal orders, stuck manual renewals, Health Check scan results, or low-traffic stores where Action Scheduler is not reliably processing subscription work.

Misconception this skill corrects

"If renewals are missing, create Action Scheduler rows or write _schedule_next_payment directly."

That can duplicate or desync WCS state. WCS 8.8 ships a Health Check scanner and Processing Reliability settings. Use the subscription object APIs, built-in Health Check tooling, and Action Scheduler configuration before inventing custom queue runners.

When to use this skill

Trigger when ANY of the following is true:

• The user mentions WooCommerce > Status > Subscriptions, Health Check, Resolve, missing renewals, automatic-renewal candidates, or scan/cancel scan.
• Code contains wcs_health_check_candidates, wcs_health_check_runs, wcs-health-check, RemediationAdvisor, ToolRunner, CandidateStore, ScheduleManager, or StatusTab.
• The store has renewal delays, DISABLE_WP_CRON, low traffic, or asks about Dedicated processing / Web cron support.
• Code contains wcs_dedicated_queue_enabled, woocommerce_subscriptions_queue_rotation, wcs_external_trigger_rate_limit_window, or /subscriptions/job-queue.