Introduction
Once a new package version is uploaded to a repository, it becomes available for users to access and download directly from the repository. However, in some cases, the newly uploaded version of the packages does not appear on the Packages page. This discrepancy can lead to confusion among users who expect to see the latest version listed under the Packages page after a new version is available within the repository.
Resolution
The update process for package versions on the Packages page is managed by the Metadata service, which utilizes an event queue to manage these changes. To successfully reflect the new version, the relevant event must be added to the Metadata event queue. If there are failures occurring within the Artifactory metadata event queue, this could hinder the update from taking effect.
To resolve the issue mentioned above and ensure that the newly uploaded version is visible on the Packages page, the 'Re-index paths on Metadata Server' API may be used. This API will re-send the Metadata events to the Metadata service, allowing the latest version to be accurately displayed under the Packages page.
If this issue reoccurs, contact JFrog Support for further investigation.