The item is installed, you noticed there’s a new version, and the updates screen doesn’t offer anything. Before investigating: check whether the item is compatible with the Auto Updater. Not the entire catalog is, and what falls outside simply doesn’t show up: it’s not a failure, it’s scope.
On the item page, the UAU Ready seal tells you whether it’s compatible.
2. The token isn’t valid
If in the item shows up, not just one, the suspect is the token, not the items. An expired token, one that was regenerated, or one tied to an old address makes the plugin run without ever finding anything. The details are in Auto Updater token.
3. The new version hasn’t reached the catalog yet
The author published, the catalog hasn’t received it yet. This is normal lag, explained in why the version here can differ. Confirm on the item page what the current version is here: if it matches the one you have installed, there’s nothing to update.
4. The item was installed under a different folder name
This is the hardest one to spot. Recognizing the item depends on it being in the folder with the name the author uses. If at some point the folder was renamed (by a manual install, a migration, a restored backup), the item becomes a different plugin in the system’s eyes.
The tell: the plugin shows up normally in the WordPress list, but never in the Auto Updater. The fix is to reinstall through the normal path, letting the ZIP create the folder with the original name.
5. Dashboard cache
The WordPress updates screen caches the result for a few hours. If the new version just landed, this could simply be it. Force the check by clicking Check Again under Dashboard > Updates.
Where to look before opening a ticket
Settings > Ultrapack Auto Updater > Logs. Every attempt gets logged, with the reason. In practice this log usually tells you which of the five cases above is yours. And if it doesn’t, that’s exactly what needs to be attached to the ticket.
