by Quade » Fri May 27, 2022 11:29 am
So, normal cycle when using headers:
1 - Download headers
2 - Headers fed to database - some might be incomplete.
3 - Download Headers later
4 - Headers fed to database - if new headers complete the files from #1, the files get marked complete.
5 - Repeat forever.
- When you download headers, you're getting a snapshot of what the server reports it has at that moment.
- When you download headers again later, you're updating that snapshot in the header database/
- So the longer you wait between header updates, the less accurate what's shown in Newsbin's list will be.
- Headers tell Newsbin the current state of the group on the server.
If the headers you're looking at are incomplete and say a day old and you've been updating headers then they might really be incomplete.
This isn't factoring in whether the server is telling the truth about headers too. NZB's come from a different source and don't depend on headers at all.
You could have a case for example where the NZB is complete but the headers report by the server will never complete. You can also have cases where the NZB reports as complete but parts of the file can't be downloaded from the server.
I'll load a group to display, see some of the newest files show incomplete, download headers again, and see them show complete now. The point is you control how current Newsbin's header databases are.
What version are you using?
Keep in mind, incomplete doesn't mean the files won't work. That's where PAR files come in. They can repair files with missing parts.