This is something I thought I accounted for, but hadn't really tested until encountering an actual fail while scraping. The scraper catches the error and displays it in the status area, but doesn't move on.

What should happen: the request fails, the scraper puts it in the retry array and moves on. When the current queue is finished move on to the retry array.

I've been slowly rewriting the script, so I'll have it fixed when that's complete.

Applied a quick fix after finding the flaw in my code. Too lazy to run it through some tests, hopefully it works.