Checked cache settings for Maven Central:

Unused Artifacts Cleanup Period (Hr) 720
Metadata Retrieval Cache Period (Sec) 43200
Assumed Offline Period (Sec) 300
Missed Retrieval Cache Period (Sec) 7200

These are the defaults and I could not find any recommendations on Maven Central which would say what they would consider abuse of service. what if I set metadata refresh period to 2 hours instead of the current 12? Or is it OK as is and you are OK with flushing cache manually before building? I don't think we can set the timeout too low as we may get blocked for abuse. I can start a discussion with Maven Central if needed to check the recommended terms if we decide we need a low cache value.

ack, will do

can you check our current timeout settings in Artifactory and adjust if needed?

I believe that artifactory has a timeout that controls this timeout. When it tries to retrieve an artifact from an remote repository (Maven Central, for example) and it fails, it won't try again till the timeout expires. The default value is 43200 seconds, 12 hours, see "Missed Retrieval Cache Period" here:

https://www.jfrog.com/confluence/display/RTF/Advanced+Settings

I'd suggest to reduce this timeout, 12 hours is too high. It is also good practice, in my opinion, to wait till the artifacts are available in Maven Central before submitting the patches that use them to gerrit. This way you avoid this timeout completely. For example, when I release version 4.1.5 of the API model I wait till it is available here:

http://central.maven.org/maven2/org/ovirt/engine/api/model/4.1.5/

Only when it is there I submit to gerrit the patches that use it.

Yes but now I have rights to trigger cache sync myself so good enough fix for me.

does it still happen?