Broken files marked as successful

[dnzbk]

Is there already an issue for your problem?

• I have checked older issues, open and closed

NZBGet Version

v24.3-stable

Platform

All

Environment

Any

Current Behavior

From the email:

I recently ended up in a weird situation with nzbget v24.3 where a group was marked as successfully downloaded/post-processed although there were broken files (missing articles) and several out.tmp files like 213.out.tmp.

I think what triggered this was the removal of an expired news server account during the download (after which I reloaded nzbget):

- The download of the group was already done but nzbget had trouble getting the last articles: one of my news servers had trouble downloading a few articles and the other one had authentication errors because my account had expired.

- When I removed the expired account and reloaded nzbget, the download was immediately marked as successful. However, at that point, there were several tmp files and broken rars in the group folder.

- I later tried post-processing again, to no avail.

- I ended up selecting "download again", which did the trick: a few articles were missing but the repair worked and the group was complete.

Expected Behavior

Broken files must not be marked as successful or NZBGet should handle this exceptional situation in some other way.

Steps To Reproduce

No response

Logs

No response

Extra information

No response