Scheduling safe WordPress core and plugin updates
Run immediate crash-safe updates, schedule routine maintenance for off-peak hours, and let high-risk security fixes bypass the queue safely.
6 min read
Triggering one-click updates
Immediate one-click updates and crash-safe rollback are included on Free and paid plans. When updates are available, they appear in your website overview grid. You can trigger updates for individual plugins, themes, or the WordPress core in a single click. The agent plugin installs the update, re-enables the plugin if WordPress switched it off, performs its immediate health check, and reports the result in real time.
Host backups and cache handling
When a site is connected to a supported host (Cloudways, Kinsta, or WP Engine), Destiny Manage takes an on-demand host backup before the update runs, and the update waits for that backup before it starts. After a successful update, the host cache is cleared automatically so your checks and visitors see the new version. On SiteGround and Hostinger the cache is cleared through the connector plugin instead, with no host connection needed. You can turn backup-before-update and cache clearing on or off per hosting account, or override them per website in that website's Hosting settings. Sites that are not on a connected host are never affected by any of this.
Scheduling an update for later (paid plans)
Starter and higher plans can avoid updating active client sites during peak traffic hours. Next to the 'Update all' button on a site's detail page, use the 'Schedule for' date/time field and the update runs then instead of immediately. This is a one-time date/time per update batch, not a recurring weekly window.
High-risk vulnerability patches run immediately
Destiny Manage cross-references every installed plugin and theme, plus WordPress core, with the Wordfence Intelligence vulnerability feed. Inactive extensions are included because their files still exist on the server. When a high or critical issue has a vendor-fixed version that WordPress reports as installable, the fix is queued immediately without waiting for a routine schedule or an agency click. Existing immediate work is not duplicated, and a scheduled update for the same component is promoted to run now. License-blocked updates and vulnerabilities without a vendor fix remain visible instead of being attempted blindly.
Post-update page verification (paid plans)
On paid plans, key pages are snapshotted before an update batch runs and re-checked once it finishes. A page that was healthy before and broken after is reported as a regression, attributed to the update batch that caused it. Bulk updates share one snapshot, so updating ten plugins still produces a single before-and-after comparison. When the server-side error behind a broken page points at a plugin in that batch, the alert names it as the confirmed culprit, and an AI-written diagnosis explains what happened and the recommended next step. The number of pages verified scales with your plan: 5 on Starter, 10 on Growth, and 15 on Scale.