When the new puppet module version is published, it takes a long time before the version is available for download though it is available in the UI. The reason behind is currently, the virtual repository metadata calculation partially relies on using an internal cache for an aggregated virtual repo metadata calculation.
This can cause some confusion and returns packages not available or 404s responses for the download requests or while listing the version we may see the missing version on successfully deployed Puppet modules (packages) to the underlying local repositories. Meaning requesting those will work right after deploying the packages to the local repositories, however, it will only work after the internal virtual cache has been time out and rebuilt.
The reason why the packages are not available is since there's a behind-the-scenes logic that takes care of merging/rebuilding the Puppet Virtual Repository cache only after a certain "quite period" - internal quiet period for recalculating that metadata that defaults to 30 minutes.
We could overcome the issue by set artifactory.puppet.reindex.period=1 under $ARTIFACTORY_HOME/etc/artifactory.system.properties file and restart the instance.This will effectively change the quiet period to one minute rather than 30 minutes which would make the packages to be available once deployed with latency.