Migration and Reindex Review

Migration scope

Some releases or configuration changes may require database migrations, Knowledge Base reindexing, cache rebuilds, or refreshed derived context. Treat that work as part of the update plan, especially when agents, search, support replies, or workflow decisions depend on current source material.

Reindex decision

Decide which sources must be refreshed after plugin updates, policy edits, imported playbooks, provider changes, or large WooCommerce catalog changes. Pair this with update and rollback, backup and staging workflow, and Knowledge Base Sources so the team knows what should be current before automation resumes.

Post-update verification

After migrations or reindexing, run a small set of read-only prompts, source citation checks, diagnostics, and workflow dry runs. Do not restart customer-facing agents, storefront panels, or write-capable automation until the refreshed context produces expected results.

Owner and cadence

• Primary owner: support lead or site administrator responsible for triage and evidence handling.
• Review cadence: when an issue is reported, before support contact, and after recovery to improve the runbook.
• Escalate when migrations, source reindexing, cache rebuilds, or refreshed context fail before production workflows restart.

Production checklist

• Identify migrations, Knowledge Base reindexing, cache rebuilds, and refreshed context required by the update or configuration change.
• Run citation checks, diagnostics, read-only prompts, and workflow dry runs before restarting agents or write-capable automation.
• Capture exact timestamp, affected user, affected screen, SophMate version, WordPress version, PHP version, and reproduction steps.
• Redact provider keys, credentials, payment data, private customer details, and raw logs before support handoff.

Acceptance checks

• Source indexes, cached context, and migrated data are current before production workflows resume.
• The team knows which modules remain paused if migration or reindex verification fails.
• The support report lets another operator reproduce or triage the issue without receiving secrets.
• The team knows whether to escalate to hosting, provider support, CodeCanyon support, or internal operations.

Common mistakes

• Restarting agents or automation after an update before confirming migrations, source indexes, caches, and citations are current.
• Retrying or changing settings repeatedly before preserving the exact error report, timestamp, and affected screen.
• Opening support requests with raw logs or vague descriptions instead of redacted diagnostics and reproduction steps.

Related operations

• Coordinate with Update and Rollback.
• Review source ownership in Knowledge Base Sources.
• Use Incident Response Runbook when production behavior is affected.
• Use Contacting Support before opening a support request.
• Use Support SLA and Escalation Matrix before customer-visible support routing.
• Use Error Reports and Support Codes before redacting or sharing an error report.
• Use Migration and Reindex Review before restarting workflows after updates.
• Use Post-Incident Review and Prevention before returning paused work to normal scope.
• Use Changelog and Release Note Review before release decisions.