by DThor » Sun Feb 10, 2013 9:01 am
Next time it happens, look in the logging tab for relevant messages. Don't delete anything just yet, it's far more likely to simply be chunks missing on the server or a timeout rather than pooched data files. You can set your retries to something low, like 1, if it's currently set higher - this is how many times newsbin attempts to get missing chunks(for example if the post is currently being uploaded). It's also possible there simply aren't enough pars to repair the particular post(say, resulting from a dmca takedown) and newsbin is trying to save you the wasted download. Essentially, if a post gets 'stuck', that's supposed to be newsbin telling you something is up with this post and it requires your attention. The status column, the painted download queue progress and the logging tab are the goto places for this.
I just picked up on the 'auto download' part of your question. If you have a really massive backlog of 'stuck' posts, that might cause problems too.
DT