Requirements and responsibilities
Have named ownership of the domain, selected xCloud team and site, and WordPress administrator access. For this scenario, agree who supplies the data and signs off: A checkout extension update causes failures while orders keep arriving.
xCloud agent capability boundaries · WordPress roles and capabilities
Use a compatible Nginx or OpenLiteSpeed stack for native WordPress. Verify current server resources, plan eligibility and each selected plugin or service license and requirements before installing; a Docker server does not host a new native WordPress site.
xCloud agent capability boundaries · WordPress plugin administration
Prepare a safe test identity and a completed, accessible backup before consequential changes. The important failure to plan around is: Blind database restore can delete paid orders.
Illustrative situation
Illustrative scenario, not a customer case study: A checkout extension update causes failures while orders keep arriving. Checkout works on the recovered path and every newer order is accounted for.
Choose the approach
Choose forward fix versus restore after tallying post-backup orders. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · WordPress roles and capabilities · xCloud WooCommerce hosting
Keep application setup, domain/DNS ownership, mail delivery and external integrations with their named administrators. Use a plain documented path when a proposed integration cannot be demonstrated end to end.
xCloud agent capability boundaries · WordPress plugin administration
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Stop risky changes and export order evidence
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Stop risky changes and export order evidence; exact site identity, named approver and controlled sample data.
- Action
- Stop further extension changes and record failing checkout step, gateway event and newest paid order. Preserve logs and current order export.
- Expected result
- The team understands failure and data at risk.
- Verify
- The team understands failure and data at risk. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If orders are still arriving, provide a staffed alternative while diagnosing.
Sources: WordPress roles and capabilities · WooCommerce testing orders · Site backups in xCloud
Step 2 of 5
Identify the last healthy backup and current order delta
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Identify the last healthy backup and current order delta; exact site identity, named approver and controlled sample data.
- Action
- Compare last healthy backup time with current WooCommerce orders and provider payments; evaluate a forward fix before rollback.
- Expected result
- The store owner sees the order delta.
- Verify
- The store owner sees the order delta. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If the delta is unknown, do not approve a database overwrite.
Sources: WordPress roles and capabilities · WooCommerce testing orders · Site backups in xCloud
Step 3 of 5
Test a repair or copy restore on safe target
- Where
- xCloud Site Backup dashboard
- Permissions
- Named xCloud team/site administrator; confirm target and scope.
- Inputs
- Test a repair or copy restore on safe target; exact site identity, named approver and controlled sample data.
- Action
- Prepare a restricted target with mail, fulfillment and payment effects quarantined before restoring a candidate backup in the dashboard. Test checkout only with its own sandbox configuration.
- Expected result
- A known-good application state can be compared without replacing live data.
- Verify
- A known-good application state can be compared without replacing live data. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If safe copy still fails, investigate provider or configuration rather than repeating restore.
Sources: Site backups in xCloud · xCloud restore backup to another site · xCloud agent capability boundaries · WooCommerce testing orders
Step 4 of 5
Approve exact in-place recovery only with owner decision
- Where
- xCloud Site Backup dashboard
- Permissions
- Named xCloud team/site administrator; confirm target and scope.
- Inputs
- Approve exact in-place recovery only with owner decision; exact site identity, named approver and controlled sample data.
- Action
- Obtain explicit owner approval for target, backup and how newer orders are preserved or replayed before any in-place restore.
- Expected result
- The recovery action has a documented data decision.
- Verify
- The recovery action has a documented data decision. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If reconciliation is impossible, keep working on a forward fix.
Sources: Site backups in xCloud · xCloud restore backup to another site · xCloud agent capability boundaries · WooCommerce testing orders
Step 5 of 5
Reconcile payments, stock and notifications afterward
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Reconcile payments, stock and notifications afterward; exact site identity, named approver and controlled sample data.
- Action
- After the chosen repair, compare order statuses, stock, payment settlement and customer messages against provider records.
- Expected result
- Every paid order has an accounted-for outcome.
- Verify
- Every paid order has an accounted-for outcome. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If a mismatch remains, keep the incident open and reconcile with store operations.
Sources: WordPress roles and capabilities · WooCommerce testing orders · Site backups in xCloud
Maintenance
Assign a cadence for selected WordPress core, theme and plugin updates, review version-based findings and retest the path in this guide. In particular, repeat: Checkout works on the recovered path and every newer order is accounted for. A chat prompt is not a scheduled task.
Manage WordPress updates with Updates Manager · Vulnerability Checker in xCloud
Record actual backup completion, storage access and responsible staff. Recheck connected application and provider behavior after changes rather than relying on a site health status alone.
Recovery decisions
Before restoring, compare the chosen recovery point with newer business records. Blind database restore can delete paid orders. Use the xCloud dashboard for native restore only after the owner approves target and scope; reconcile or preserve newer data first.
Validate the restored copy with representative content, authentication, HTTPS and this guide’s business acceptance test before moving traffic or closing the incident.
AI handoff
Connect xCloud MCP through the current documented profile and grant only the scopes needed for the selected team. Discover tool schemas first. Read resources to plan; require approval for any supported write. Use returned dashboard URLs for manual work. The packaged REST wrapper accepts GET requests only.
Supported scope
- Confirm requirements and inspect resources mcp · read
Discover the connected profile and operation schema first; only teams granted to the connection are visible.
Checkpoint: Confirm exact team, server and site identity. Use dashboard_url returned by the resource; do not invent a dashboard link.
Operation identifiers and scopes to discover
teams.index, servers.show, sites.show
Scopes: read:servers, read:sites
xCloud MCP documentation and connection profiles · xCloud agent capability boundaries
- Review a WordPress business journey app · manual
Application data and observed transactions cannot be inferred from xCloud resource reads. Use authorized test accounts and the application or provider evidence.
Checkpoint: Record the test identity, timestamp, expected outcome, observed result and owner decision.
- Restore a backup dashboard · manual
Native and Docker restore operations are dashboard-only. An in-place Docker restore replaces current data.
Checkpoint: Use Site → Site Backup → Previous Backups → Restore Backup (or Restore to Another Site where offered). Confirm exact target and recovery point before proceeding.
xCloud agent capability boundaries · Back up and restore Docker apps
Copyable agent brief
Manual checkpoints
- The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: Prepare a restricted target with mail, fulfillment and payment effects quarantined before restoring a candidate backup in the dashboard. Test checkout only with its own sandbox configuration.
- The business owner compares the controlled sample with this observable result: The recovery action has a documented data decision.
- Staging push/pull, native backup schedules, restores and cache-setting edits require the authorized xCloud dashboard operator; the packaged REST wrapper is GET-only.
Feature coverage
- business-acceptance (covered): Checkout works on the recovered path and every newer order is accounted for. Approve exact in-place recovery only with owner decision
- recovery (covered): Blind database restore can delete paid orders. Reconcile payments, stock and notifications afterward
Sources
- xCloud agent capability boundaries
- WordPress roles and capabilities
- WordPress plugin administration
- Site backups in xCloud
- WordPress hardening handbook
- xCloud MCP documentation and connection profiles
- xCloud WooCommerce hosting
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud
- WooCommerce testing orders
- xCloud restore backup to another site
- Back up and restore Docker apps