It's stuck. Investigate and fix.
14:51 <samplet> Hi SWH! According to the Web interface, the nixguix loader hasn’t had a successful visit of Guix’s “sources.json” in over a month. 14:52 <samplet> That seems to be true of nixpkgs, too. 14:54 <+ardumont> samplet: yes, it's only partial because there are some types of origins referenced that's not dealt with yet 14:54 <+ardumont> and also because some origins ends up being 404 14:54 <+ardumont> so as there are lots of origins in those manifest, there is a high probability it won't succeed 14:55 <+ardumont> but it does its best to ingest the remaining part 14:55 <+anlambert> ardumont: samplet is right, check visits reports of guix for instance, they are all red since november https://archive.softwareheritage.org/browse/origin/visits/?origin_url=https://guix.gnu.org/sources.json 14:55 <samplet> ardumont: Ah. That explains all the yellow! But there’s nothing but red in November. 14:55 <+anlambert> and it seems the loader is stopped since one month 14:56 <+ardumont> heh, so that needs an unbreaking task ;) 14:56 <+ardumont> thx for the heads up 14:56 <+ardumont> (in any case ;) 14:57 <samplet> I noticed because Guix’s SWH coverage tracking shows a noticeable drop for commits from November. 14:57 <samplet> Thanks for taking a look!
As olasd  pointed out, maybe start by looking at the scheduler part. Is nixguix visit still scheduled?
15:03 <+olasd> is anything even scheduling the nixguix loading tasks now?