Thanks everyone!
The scoring system had a query that got (very) inefficient if it was behind, eventually so slow that it never could run to completion (and/or something changed in the database, maybe because this particular table got bigger than expected).
It’s been fixed now and the scorer is working on catching up!
(I also added more metrics for the monitoring system to look after…)