Features / WordPress fleet updates

Let routine updates move. Review the changes that need you.

Set update rules for the workspace and override them per site. Security, regular releases and page builders have separate lanes; detected breaking changes wait for a person.

The workflow on screen

Understand why an update runs or waits

The current update queue separates automatic work from changes waiting for you. Its rules explain delays, maintenance windows and breaking-change holds. Your configured lanes determine what can run.

The usual regular delay is three days from first detection; page builders wait for approval by default or can use a seven-day delay. Checks and scoped recovery reduce risk without guaranteeing an unbroken site.

Understand why an update runs or waits. Real IrmaWP interface with fictional demo data.
Real screenshot · Dark mode · Fictional demo data · November 16, 2026. Open the full demo screenshot in a new tab
Automatic updates, with clear rules

Routine updates move. Risky changes wait for you.

Choose the rules for your workspace, override them per site, or set them when you connect a site. You can require approval in any lane.

Security: act when detected

With automatic security updates enabled, IrmaWP queues detected security releases without waiting for the maintenance window. Breaking changes still require approval.

Regular: wait 3 days

Wait 3 days from first detection to leave room for hotfixes, then use the next update check and any configured maintenance window. A newer version restarts the wait.

Page builders: approve or wait 7 days

Elementor, Divi, Bricks, Beaver Builder, WPBakery and Oxygen wait for approval by default. Choose automatic updates after 7 days from first detection if that fits the site.

Before you connect

What to know

Can updates run through SSH as well as the connector?
Yes. Supported update paths include connector abilities and WP-CLI over SSH. The required connection must be available and authorized.
Can every update be rolled back?
No. Recovery options depend on the update and available backups or artifacts. Translation updates are not rolled back.
What happens when an update announces breaking changes?
When changelog analysis detects breaking changes, the update waits for a person, regardless of the lane. A failed or rolled-back update in the last 7 days pauses non-security automation on that site. Smoke checks and supported scoped recovery reduce risk; they do not guarantee an unbroken site or automatically restore its live database.
Does the wait start on the public release date?
No. The delay starts when IrmaWP first detects that version. A newer detected version restarts it. Execution waits for the next update check and, for non-security updates, any configured maintenance window.
Can SSH replace a missing connector for automatic updates?
SSH can provide supported read-only inventory and update checks when configured. A missing or unreachable connector blocks automatic applies and ordinary fleet update actions until the connection is restored.

Start with your own sites.

Connect a small portfolio, check the tools you need, and choose the plan that fits your team's work.