Troubleshooting

This page collects common problems and their fixes. If your issue is not listed, use the Documentation, Support, or Leave a review links in the Updatronix header, or ask on the plugin’s WordPress.org support forum.

The page stays on “Loading your Updatronix settings…”

The Updatronix screen is a JavaScript interface. If it never finishes loading, the interface files may be missing from your installation. An admin notice then explains: Updatronix: The admin interface is not available because the JavaScript bundle is missing. Please run npm run build from the plugin directory.

Two fixes, in order:

1. Reinstall the plugin from the ZIP file you downloaded or from WordPress.org. The distribution includes the interface files.
2. If the screen still hangs, refresh the page and check your browser console for blocked requests.

The log says “Update logging is off” or stays empty

• Open Settings and turn on Record all updates. No entries are written while it is off.
• If logging is on but the table says No update logs yet. Entries appear after WordPress runs an update., no update has run since you enabled logging. Manual updates, installs, and automatic runs all create entries; the log cannot show updates that happened before Updatronix was active.

Entries stay “Delayed” and updates take days to install

That is the Delay updates feature working as designed. WordPress waits the configured number of full days after it first sees an update before installing it automatically.

• To install sooner, lower Days to wait on the Schedule tab, or turn Delay updates off.
• The delay applies to automatic installs only; manual updates install immediately.
• Countdowns on the native Updates, Plugins, and Themes screens show the next update check, not the delay timer. Each update keeps its own timer, and details stay in Update logs.

Nothing runs on the schedule

Scheduled tasks run on WP-Cron, WordPress’s built-in task scheduler, or on a system cron job that calls wp-cron.php when WP-Cron is disabled.

1. If DISABLE_WP_CRON is set in your wp-config.php file (the main WordPress configuration file at your site’s root), WordPress does not run scheduled tasks during normal visits. Set up a system cron job that calls wp-cron.php regularly, or remove the constant.
2. Check the Auto-updates tab for notices about the constant.
3. If you use an external cron service or a cache layer that blocks wp-cron.php, make sure Updatronix’s scheduled tasks can run: the daily log cleanup, and the update check when a custom schedule is active.

Auto-update controls are locked or read-only

Locked controls mean a wp-config.php constant is in charge, and Updatronix cannot override it:

• WP_AUTO_UPDATE_CORE: locks the core mode selector. Edit the constant in wp-config.php to change core behavior.
• AUTOMATIC_UPDATER_DISABLED (true): turns off all automatic updates at the WordPress level.
• DISALLOW_FILE_MODS (true): blocks all file changes, including automatic updates.

Editing wp-config.php requires care. Make a backup first, and remove only the constant you want to stop defining.

Update notification emails do not arrive

Check the Settings → Update notifications section in this order:

1. Is Disable all update notification emails on? It suppresses core, plugin, theme, and debug emails (recovery mode is unaffected). Turn it off.
2. Is Manage update notifications on, with a valid address in Send notification emails to? Invalid addresses are dropped when you save.
3. Are the right Notification types ticked? WordPress sends one email per run: the detailed report when available, otherwise the usual summary.
4. The email may be missing because WordPress itself did not send one (an SMTP failure, for example), or because a spam filter caught it. Recovery mode emails still go to the site administrator after a fatal error.

The update check never runs at my preferred time

Recurring WordPress schedules use fixed-length intervals. The Schedule tab explains: Recurring runs may shift by up to one hour after daylight saving transitions, since WordPress recurrences are fixed-length intervals. The preferred time anchors the first run; later runs follow the interval.

The export fails or is truncated

• Too many exports started recently. Wait a minute, and then try again.: exports are rate-limited; wait and retry.
• The export is too large and was stopped. or a truncation notice: narrow your filters to export fewer rows.
• This export session has expired. Start a new export.: the output is only kept for 15 minutes; generate a new one.

See Update logs for the export steps.

Deletion or cleanup fails

• A single entry that will not delete shows: The log entry could not be deleted. Try again or check your database connection.
• Clear all logs failing shows: Could not clear logs. Try again.
• Both point to a database problem. Check that the site’s database is reachable and that the update log table exists. If it is missing entirely (after a partial restore, for example), deactivate and reactivate the plugin so activation recreates it.

Multisite problems

• “Updatronix was activated on a subsite”: activate network-wide from the Network Admin instead.
• No Updatronix menu on a subsite: expected; subsites never load the Updatronix interface. Use the Network Admin.
• Settings seem to have no effect: on multisite, settings, schedule, and the log are network-wide and set from the Network Admin.

See also: Getting started · Update logs · Schedule · Settings · Multisite