Rescan issues

[T-prog3]

I recently ran Force rescan on some blogs and noticed first of all that this function doesn't automatically reset to False after its done. But also when i manually set it to False in Blog Settings or config file then the software continues as if its still True and look through the complete blog and wont stop at last complete crawl or latest post date. It took hours to complete only 10 new posts.

[thomas694]

I wouldn't classify the missing automatic reset as an error.

Once a Force rescan has started, it needs a complete error-free run, either the current one or any future one, to set a new LastId (Last Complete Crawl/Latest Post are irrelevant).

So in your case you can set LastId to any current post id to stop the long scans.

[T-prog3]

The main issue is that even when i complete the download it still look through full blogs on every run so far. And every post show up as already downloaded, skipping and with the rate limits this can take hours to complete.

One thing i miss is some sort of indicator that show if it download the blog as normal or with Force rescan enabled in the download Queue. Like a F before the star ratings or something. I know that you can look for the check mark in details but this can be tedious with a large amount of blogs and in my case none have that check mark and still it look through it all.

I was under the impression that LastId was the id of the Latest Postdate found and that the scan wouldn't go beyond this date unless rescan was enabled? So does the downloader have to encounter this id to stop? And what happens if this id got removed by the blog or twitter/tumblr?

[devilspeech]

I've been having this same issue for a while where some Twitter accounts seemed to be force rescanning despite having the option turned off. Now with the latest update (v2.15.0) I do see these accounts have an [F] next to them even with force rescan off with seemingly no way to remove it. I have tried re-checking force rescan in the settings, scanning the account and then un-checking after it's done, but the [F] just sticks around regardless and they continue to take ages to scan. I can't tell if there is any pattern to which accounts are affected, it seems more or less random. But even a handful of accounts with 10k+ posts force rescanning each time can cause backups to take days to complete with Twitter's rate limit.