Run Your First Scan

Your first successful full scan creates the baseline that the rest of the product relies on. Until that baseline exists, inventory tables, source drill-down, and Refactor previews cannot be treated as complete.

1. Open the Scans tab.
2. Start a full scan.
3. Wait for the run to finish. You may see statuses like queued or running before it reaches completed.
4. Check that the latest completed scan time matches the window you care about.
5. Open the inventory views and confirm indexed rows appear where you expect them.

What a healthy first scan looks like #

• The latest full scan finishes with a completed status.
• The finished timestamp is recent enough for the work you are doing.
• Blocks, Patterns, Template Parts, or Navigations return indexed rows.
• Source drill-down opens exact sources instead of an empty modal.
• Refactor preview scope can now rely on the same baseline instead of stale content guesses.

If the baseline looks stale or incomplete #

Rerun a full scan before reporting, previewing Refactor batches, or applying replacement work if the latest completed baseline is too old for the work you are doing, if the last run failed or was cancelled, or if recent content changes are not reflected yet.

CLI checks #

If scan controls are read-only or you need a quick CLI check, these commands are the supported path:

• wp dxm-block-toolkit scan --dry-run previews scan scope without writing index data.
• wp dxm-block-toolkit stats --format=json returns normalized inventory stats for automation or quick verification.
• wp dxm-block-toolkit doctor --format=json runs read-only index integrity checks for the current site.

Where to go next #