i do not think its a repo thats at fault, as it seems to trigger when all the repos have been "updated" and the info is to be integrated with existing data...