The site stays "pending" after connecting

The connect key is valid for 15 minutes; generate a fresh one if longer has passed. Otherwise the site cannot reach MegaManager: check that outbound HTTPS is allowed, and that a security plugin or firewall is not blocking the WordPress REST API.

The site shows "disconnected"

Some cause has broken the link:

The plugin was deactivated or deleted.
The site is down or unreachable.
Someone pressed Disconnect on the WordPress side.
The site stopped answering us. Note that a site with no visitors does not count: when a site goes quiet MegaManager calls it directly before deciding, so only a site that genuinely fails to answer is marked.

Open the site and press Sync — a successful sync marks it connected again. If it fails, the error names the reason.

You do not have to do this for a site MegaManager disconnected by itself. Those are re-checked about every half hour, and a site that answers is restored on its own, with a "back online" notification. A disconnect you asked for is not undone this way: after pressing Disconnect, deleting the plugin, or deactivating it, the site stays disconnected until you reconnect it from WordPress.

The feedback overlay disappeared

Usually an expired review link. Those last 12 hours by design, and the overlay removes itself rather than sitting there dead.

If it should be permanent, grant your WordPress user access on the Feedback tab instead of using a link. See Client feedback.

Also check the feature is still enabled for the site, since that switch turns it off for everyone at once.

A backup fails

The reason is shown on the Backups tab. In order of how often they happen: not enough disk space on the site, PHP time or memory limits, and an unreachable site. Very large sites sometimes need their host's PHP limits raised before a first backup will complete.

An update failed

The site's Activity log has the per-item result. A plugin that fails to update usually says why — a file permission, a failed download, or a PHP version it will not run on. Plugin updates keep a rollback point, so a plugin that updated and then broke the site can be put back from the Updates tab.

Auto-updates are not running

Check, in order: that they are enabled for that site, and that the plugin is not on the denylist. A lack of traffic is no longer a reason — WordPress only runs its scheduler when somebody visits, but MegaManager asks quiet sites to run their updates rather than waiting for a visitor.

Something changed and the site does not show it

Clear the caches from the Cache tab. If it persists, the site may be behind a CDN or host-level cache that MegaManager does not control.

Nothing here matches

Take the message you are seeing and the site's Logs tab, and contact us. The logs are where the connector records what it tried and what came back.