Action Scheduler 4 cleanup behavior can reduce table bloat, but a care plan should preserve enough failed-job evidence before old actions are removed. The goal is a monthly owner report, not a larger database forever.
Use this for stores where scheduled actions touch renewals, payment retries, email delivery, fulfillment, CRM sync, analytics uploads, and reporting jobs.
Quick answer
Action Scheduler 4 Cleanup Policy for WooCommerce Care Plans should be handled with a narrow evidence-first workflow: pick cadence, export failures, classify impact, then verify the result before making broader changes.
What to check first
- Choose a reporting cadence that is shorter than the cleanup window for failed actions.
- Export failed action groups with age, count, sample IDs, last error, owner, and decision.
- Classify each group as revenue, customer communication, fulfillment, tracking, maintenance, or noise.
- Store a compact report outside the Action Scheduler tables before cleanup removes old rows.
- Review the report with the owner and turn recurring failures into tickets or vendor follow-ups.
Diagnostic table
Use this table to keep the work practical. It connects the symptom to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|
| Pick cadence | Choose a reporting cadence that is shorter than the cleanup window for failed actions. | The report runs before cleanup removes useful failed-action evidence. |
| Export failures | Export failed action groups with age, count, sample IDs, last error, owner, and decision. | Every recurring failed group has an owner and business impact label. |
| Classify impact | Classify each group as revenue, customer communication, fulfillment, tracking, maintenance, or noise. | Noise groups are documented so they stop distracting the team. |
| Store report | Store a compact report outside the Action Scheduler tables before cleanup removes old rows. | Critical groups become tickets, vendor cases, or monitored fixes. |
Why this usually happens
- Database cleanup improves performance but removes history support teams may need.
- A care-plan report gives business context to hooks that otherwise look technical.
- Monthly reviews catch slow queue drift before checkout or email symptoms appear.
- A failed action can be harmless on one store and revenue-critical on another.
Field notes
- Keep exported reports lean. The owner needs impact and decision, not thousands of raw rows.
- Tie failed jobs to service areas such as payment, leads, email, and fulfillment.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
report_date=$(date -u +%Y-%m-%d)
wp action-scheduler list --status=failed --format=json > action-scheduler-failed-$report_date.json
jq 'group_by(.hook) | map({hook:.[0].hook,count:length,oldest:(map(.scheduled_date_gmt)|min)})' action-scheduler-failed-$report_date.json
# Add owner, impact, and next action before cleanup removes evidence.
Safe fix order
Do the work in a sequence that makes each result easy to prove. Stop if a step produces new evidence that changes the incident scope.
- Pick cadence
- Export failures
- Classify impact
- Store report
- Review owner actions
What to tell the client or owner
Give the owner a short queue health report that names what matters and what is safe to ignore.
Production verification checklist
- The report runs before cleanup removes useful failed-action evidence.
- Every recurring failed group has an owner and business impact label.
- Noise groups are documented so they stop distracting the team.
- Critical groups become tickets, vendor cases, or monitored fixes.
Mistakes to avoid
- Do not judge the fix by one browser or the homepage only.
- Do not delete evidence before recording usernames, file paths, timestamps, and response headers.
- Do not add a cache, security, or tracking plugin while the original problem is still unclear.
- Do not leave test users, temporary debug logs, or broad API keys active after verification.
When HandL WP should help
Bring in help when this affects leads, checkout, search visibility, malware risk, paid media reporting, or a client production site. HandL WP can trace the issue through WordPress, hosting, cache, tracking, and Search Console, then verify the workflow after the technical fix.
If this is active on a production site, add Action Scheduler monitoring to a care plan.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references