That can occur if you happen to hit one of our repository servers during the time it is replicating the new content to it. It is recommended to run the pull task a couple of times during different hours of the day to work around that, as there is no way to know which repository server you might hit and when specifically the replication is completed. We do not disable the repositories during replication so that most content is still available.
Was my reply helpful? If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?