Run a reviewed Safe Updates queue
Review an update group and check its result and recovery status.

Video coming soon
Your next step is ready.
Follow the complete written guide below.
The video will join it here when it’s ready.
Before you start
- An EMCP Cloud account on a paid plan (Freelancer, Agency or Enterprise) and owner access.
- Connected practice sites with Gateway access enabled and current EMCP versions.
- A disposable staging site, independent backup and planned maintenance window.
Let’s do this, step by step.
Step 01
Enable and check readiness
Enable Tools → EMCP Modules → EMCP Cloud → Cloud Safe Updates and Save changes. In Account → Safe updates choose Check websites.
On the practice site, open EMCP Tools, Tools, then EMCP Modules. In EMCP Cloud, enable Cloud Safe Updates and save. In your Cloud account, open Safe updates and choose Check websites. Resolve readiness problems before creating a queue.
Step 02
Review the update groups
Choose Check for updates, select exact items, Review selected updates and Plan safe update.
Check for updates and select only the items you want. Choose Review selected updates and inspect the groups. Related plugins may be updated together. Use Plan safe update to review before starting.
Step 03
Review checks and maintenance
Review mandatory home/login checks and up to five same-site public HTML paths returning 200 without redirects. Consent to maintenance before Start safe updates.
Review the pages that will be checked before and after updates. These are response checks, not a visual or payment test. Read the maintenance notice: visitors, checkout and admin work may pause while a group runs. Start only when that interruption is acceptable.
Step 04
Follow background progress
Observe baseline, maintenance, recovery snapshot, installation and repeated live checks. Work continues after closing the account tab.
Follow the stages as EMCP checks the starting state, prepares recovery, applies a group and checks the live result. This Cloud queue continues in the background. If a failed group is restored, earlier successful groups stay updated.
Step 05
Handle recovery deliberately
Read per-group outcomes. Stop queue restores the current group. Attention may offer Retry recovery and stop queue after fixing the cause. Preserve recovery files.
Read every group’s final result. Use the queue’s stop and recovery controls when needed. Attention is not a successful rollback. Investigate the cause before retrying recovery, and leave the recovery files in place.
Step 06
Verify the site yourself
Test key pages, admin, forms and checkout on staging. Use Alerts for future notifications and keep independent backups.
Open the website and check important pages and interactions yourself. A passing response check cannot prove a form or payment works. Keep your independent backup. Configure Alerts if you want notifications for future queues.
You’re done when…
Every group has a final result and the affected site has passed manual checks, with recovery issues documented.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.
A brief becomes a real page.