DevXMachina
Menu
EN RO
EN RO

Troubleshooting

Most support issues come down to baseline scans, license state, freshness, misunderstood inventory scope, or Refactor batches that need another review step. Start with the section that matches the symptom you are seeing.

No indexed rows after install #

  • Run a full scan at least once.
  • Check the latest scan status in the Scans tab.
  • Confirm current user has admin capabilities.
  • Treat the product as not ready for reporting until a completed full baseline exists.

Scan controls are read-only #

  • License may be missing, invalid, or expired.
  • Refresh license state from the License tab.
  • Reactivate the key if needed.
  • Use wp dxm-block-toolkit scan --dry-run if you need a read-only validation path while licensing is being resolved.
  • Refactor apply and rollback actions stay unavailable until write-enabled access is restored.

License activation errors #

  • Verify the key matches the purchase record.
  • Use the billing portal to confirm the subscription is active.
  • Retry after a short delay if network conditions were unstable.
  • Refresh license state from the License tab after activation.

Unknown pattern, template-part, or navigation rows #

  • Unknown rows are follow-up signals, not automatic product errors.
  • Patterns cover reusable or synced entities and their references via core/block.
  • Template Parts and Navigations track direct references and can group unresolved targets as Unknown.
  • Rerun a full scan if content or referenced entities changed recently, then inspect the matching sources for the unresolved row.

Export seems incomplete #

  • Inventory and source exports are capped to the first 5,000 filtered rows per export action by default.
  • Narrow filters and export in smaller slices on larger sites.
  • If you need larger caps, that is a developer setting rather than a standard admin workflow.

Advanced source filters return no matches #

  • Run a fresh full scan so the attribute index is populated.
  • When filtering by block content, confirm the distinctive text fragment is actually inside the indexed block content, not only elsewhere in the page.
  • Confirm the block source row actually contains that class, ID, anchor, or scalar attribute value.
  • If the full sentence varies across sources, try a shorter distinctive fragment before assuming the index is missing data.
  • Check dot-path spelling for nested attributes, such as style.color.text.
  • Use the dedicated Attribute Path fields when the value contains spaces; compact queries do not support quoted values.

Refactor preview returned no rows #

  • Confirm the block, entity, or filter scope still matches real indexed rows.
  • Review advanced source filters or batch scope settings for over-constrained conditions.
  • Run a fresh full scan if recent content changes may have removed or renamed the original matches.

Refactor target looks invalid or wrong for the mode #

  • Confirm the Refactor mode matches the thing you actually intend to change.
  • Use block_instance for matching block instances, entity_reference for shared-entity references, and entity_definition for the shared entity itself.
  • If the target no longer resolves cleanly, rerun a full scan and rebuild the preview from current inventory evidence.

Apply was skipped after content changes #

  • A skipped apply usually means the stored content changed after preview was generated.
  • Review batch details to see which rows no longer matched the preview assumptions.
  • Rerun a full scan if the content changed materially, then generate a new preview before applying again.

Rollback was skipped or failed #

  • Skipped rollback rows usually mean the stored content no longer matched the previously applied batch assumptions.
  • Failed rollback rows need manual follow-up after you review the batch details and current content state.
  • If content drift happened after apply, rerun a full scan before deciding whether to retry rollback or handle the rows manually.

Stale or failed scan data #

  • Use the latest completed full scan as the authoritative baseline.
  • Rerun a full scan if the baseline is stale for your reporting window.
  • If the last run failed or was cancelled, treat current inventory data as potentially incomplete until a new completed baseline is available.
  • Do the same before trusting Refactor previews or apply decisions.

Advanced validation with WP-CLI #

If you need a quick CLI check, use:

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

Use these commands to validate scope, stats, or index integrity without turning this docs set into a full CLI reference.

Need billing updates or cancellation #

Use the billing portal for card updates, invoices, and subscription cancellation.

Still blocked? #

Contact support and include: [email protected].

  • WordPress version and PHP version
  • Screenshot of license status card
  • Last scan status and timestamp
  • Which inventory view or export action you were using