I ran a test scraper which confirmed the problem. I then stopped the sidekiq processes from the admin backend and upstart subsequently started them back up. I ran a test scraper again and confirmed it was fixed

I didn’t realise you could do this in the admin. That’s brilliant. @tmtmtmtm you have access to that right? Wanna just jump in and give that a go next time and let us know how it goes? Still a good idea to report here and/or in Slack that you’re gonna do it first

@chris48s This is probably the situation where 1 of the 2 workers is affect, which is why @equivalentideas couldn’t see the problem with the test scraper. I’ve restarted the workers so hopefully it’s fixed now.

I’m so sorry to bother you, I know you are busy. But if you could do that reboot again I would appreciate it. Things are not saving to the database again. I would try to fix the bug if I could, though I’m sure I would cause more problems. Thanks @equivalentideas! -Lucia

Mods - sorry to bother you again with his, but I’m getting the same error again across two scrapers. I noticed a few other scrapers are not saving anything to databases either. Is another reboot needed?