Skip to content
Help centre

What the update run messages mean

Plain-English meanings of the statuses and messages you see on a WordPress update run, and what to do about each.

Open an update run on a site's WordPress page to see each package's step and what happened. Here's what the messages mean.

Run statuses

StatusWhat it meansWhat to do
Waiting for the siteQueued. OpsDash is waking the site and waiting for it to check in and start.Nothing, unless it waits a long time (see below).
RunningWorking through the packages one at a time, for example "Working on 3 of 11: Gravity Forms, uploading the backup".Nothing. The page updates itself.
UpdatedEvery package updated and the site is healthy.Nothing.
Finished with problemsIt went through every package, but some weren't updated.Open the run to see which, and why.
StoppedIt stopped part-way and skipped the rest (Stop the run when an update fails is on, or the site didn't recover).Fix the failing package, then run the rest again.
Rolled backThe update broke the site, so its backup was restored.Check the PHP errors and what WordPress said; update by hand on staging if needed.
Needs reviewThe visual check found a page that changed more than the threshold.Compare the screenshots, then Looks fine, approve, or investigate.
FailedIt couldn't run.Read the message on the run.
CancelledSomeone cancelled it.

Package (step) statuses

  • Waiting: not started yet.
  • Updating: in progress.
  • Updated: done and the site is healthy.
  • Rolled back: it broke the site and was undone.
  • Not updated: it failed without changing anything (for example WordPress couldn't download it).
  • Skipped: the run stopped before it got to this package.

Common messages

  • "Waiting for the site to check in…" / "The plugin hasn't checked in yet." OpsDash is waiting for a check-in. Usually seconds; longer on quiet sites. See troubleshooting.
  • "Hasn't checked in for 12 hours…" The site has gone quiet. Check it's up and the plugin is active.
  • "WP-Cron is switched off on the site (DISABLE_WP_CRON)…" It only checks in when OpsDash wakes it or a server cron runs. Set up a server cron for wp-cron.php.
  • "WordPress only runs its scheduled tasks when someone visits, so quiet sites miss check-ins." As above; wake-ups help with plugin 1.3.1 or later.
  • "Update the OpsDash plugin to 1.3.1 so OpsDash can wake it…" The plugin is too old to be woken. It updates itself; or update it in WordPress.
  • "OpsDash's check from outside passed" After the update, OpsDash loaded the site's pages and they were fine.
  • "The site restored its backup straight away." / "OpsDash had the site restore its backup." The update was rolled back.
  • "The run carried on with the next package." One package was rolled back, but the site was healthy again, so the rest went ahead.
  • "Its subscription or licence has expired, so WordPress couldn't download the update." / "It has no licence key…" A premium plugin's licence needs renewing or adding in WordPress. Then run the update again.
  • "The database backup didn't finish: …" The backup failed, so no updates were applied. The reason follows (often a host time or memory limit).
  • "No database backup: this site is set to Files only." As chosen in the site's settings.
  • "Updates are held: this site's OpsDash plugin … has a backup bug…" The plugin must be updated before OpsDash will update the site. See backups and restores.
  • "Updates are held while this site's database is repaired." They carry on once the repair finishes.
  • "Held: plugin too old" (in the sites list) Same as above.

PHP errors

A run shows PHP errors before the update and after the update. An error that was already there before doesn't count against the update. If a site has a PHP error on its pages, the site's page says so.

Run labels

  • Run by hand, Maintenance window or Copied from staging: what started it.
  • Patch tried on staging / Patch copied to production: a fix prepared by an agent and tried on staging first. Promote patch copies it to production; Keep on staging doesn't.