Scan Health

Scan health tells you whether the current index is ready for operational decisions. The latest completed full scan is the baseline that matters most.

Why the last full scan matters #

DXM Block Audit treats the latest completed full scan as the authoritative baseline for freshness and trust. If that baseline is missing, failed, or too old, inventory data should be treated cautiously until a new full scan completes.

Healthy and current enough to trust #

• The latest full scan completed successfully.
• The finished timestamp still fits your reporting or handoff window.
• Inventory views load expected rows and source drill-down behaves normally.

What stale usually means #

Freshness is driven by the age of the latest completed baseline. By default, DXM Block Audit treats that baseline as stale after about 24 hours.

• A stale baseline does not mean the index is unusable, but it does mean you should think before reporting from it.
• If major content changes happened after the last completed scan, rerun a full scan before sharing results externally.

Status language you may see #

• Queued or running: the baseline is still being built.
• Completed: the baseline is available.
• Failed or cancelled: rerun before trusting results.
• Cancelling: wait for the run to settle, then assess the last completed baseline.

When to rerun a full scan #

• Before a report, export, or handoff that needs current evidence.
• After a failed or cancelled scan.
• After meaningful content or FSE entity changes.
• After operational or schema changes that require a fresh baseline.

Advanced checks #

If you need a quick CLI check, these commands are the supported path:

• wp dxm-block-audit scan --dry-run
• wp dxm-block-audit stats --format=json
• wp dxm-block-audit doctor --format=json

These commands are useful when you need a read-only or scriptable check of scan scope, normalized stats, or index integrity.