That seems like a poorly designed system. So if I’m scanning 150 pages and it jams on page 145 with this system I would have to re-scan all 145 pages again instead of just the 5 remaining pages. Is there a setting to bypass this?
Also as I was testing this it seems as the machine doesn't actually scan a new image of the previous pages it only sends them through the feeder and counts them and then starts scanning the image of the pages after it sends through the correct amount of pages that was sent prior to the jam. With that being the case the machine is keeping the image of the pages prior to the jam in the system so why make us re scan or send through the doc feeder all the previous pages if they aren't being scanned?
How i tested this. Numbered 6 pages. Damaged page 3 so it would jam. Started the scan, and when page 3 jammed i pulled it out and only added it back to the doc feeder. Resumed the scan. It finished and sent me the file with the image of Page 1,2,5,6 It didn't rescan the first two pages after clearing the jam which would have been page 3 and 4 it used the image of the original first two pages and only sent page 3 and 4 through the feeder to count them.
With that being the case I can't see any reason why to resend the pages before the jam back through, this is a waste of time.
The issue with why this isn't acceptable is that I am scanning big files that I receive from my clients. They have mixed sizes and quality of pages as they are sending me all their receipts and bank statements for the year. I have always and will always have paper jams due to the quality of paper I receive but with my previous machine ( a competitors machine ) I didn't have to send the pages that were already scanned back through. With this system I have to be able to scan the complete package completely without any jams or I will not be able to finish the file.