Origins loaded so present in the archive and in the scheduler db (table origin-visit-stats).
As those origins were not listed through a lister though, they are filtered out during the scheduler metrics update (sql routine which does an inner join).
We need to reference those origins so they can show up properly in the scheduler metrics (and thus in https://archive.s.o main page).
The simpler way seems to attach those origins with the bitbucket lister, retrofill the listed origins from origin-visit-stats as disabled ones.
And then let the remaining cogs do the rest.