To properly send sha1s to archive in azure, we are working from the result of the provenance cache.
It's working slowly.
Loading sha1s from known repositories (we already have) and send that result directly to the archiver queue should bypass that temporary setback.