Update and Rollback

Before updating

Read the release notes, confirm minimum requirements, and prepare a backup that can actually be restored. For WooCommerce stores, review active workflows, watchers, agents, provider settings, and Theme Assistant drafts before applying the update.

Staging and pause rules

Test the update on staging whenever the release touches workflows, providers, Theme Assistant, approvals, diagnostics, agents, or WooCommerce behavior. Pause automation categories when the team cannot verify the effect immediately. The update tutorial gives the operational checklist.

Rollback record

Document release version, update date, backup location, restore owner, diagnostics result, and any known caveats before resuming normal use. Pair update review with audit log review after the first production actions.

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 evidence is incomplete, private data may be exposed, production impact continues, or routing between host, provider, and plugin support is unclear.

Production checklist

• Read release notes, confirm requirements, prepare a restore-tested backup, update staging, pause risky automation, and run diagnostics.
• Document version, update time, owner, known caveats, and rollback decision before resuming normal use.
• 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

• Staging and production both pass diagnostics after the update.
• Automation, provider tests, approvals, and key public paths are verified before the update window closes.
• 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

• 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

• Follow the update tutorial.
• Use Backup and Staging Workflow before major releases.
• 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.