Maybe "Retry Failed Articles" should be run once automatically if PAR fails?

[francislavoie]

Is there already an issue for this request?

• I have checked older issues, open and closed

Platform

Windows

Describe the enhancement you'd like

Pretty frequently, I get failures that look like this:

warning	Fri Nov 29 2024 19:37:38	Skipping unpack for <file> due to par-failure
info	Fri Nov 29 2024 19:37:37	No renamed archive files found for <file>
info	Fri Nov 29 2024 19:37:37	Checking renamed archive files for <file>
error	Fri Nov 29 2024 19:37:37	Repair failed for <file>\1293293ea40f3ad9a141c5c3e9a4bde6868cc780: not enough par-blocks, 178 block(s) needed, but 143 block(s) available. Recovery files created by: ParPar v0.3.2 [https://animetosho.org/app/parpar]
info	Fri Nov 29 2024 19:37:37	Need more 178 par-block(s) for <file>\1293293ea40f3ad9a141c5c3e9a4bde6868cc780

These get stuck in my history as failed downloads. But 90% of the time, they download and finish successfully if I use Actions > Retry Failed Articles.

Is there any particular reason no retry gets triggered?

Extra information

No response

[dnzbk]

It's probably a bug. What is the version of NZBGet?
Could you also share the nzb file for testing? [email protected]

[francislavoie]

I don't think it's a new bug, it's been doing this for years. Just wanted it bring it up since this project is active again. I can pull up more details next time I'm at my PC (day or so if I remember). But I doubt it can be replicated, probably provider-specific which file results you get etc.

[dnzbk]

Thanks, I'll take a look.

[francislavoie]

deleted

deleted

Notice that the download failed at Sun Dec 08 2024 21:05:20 then I clicked Retry Failed Articles just now at Mon Dec 09 2024 01:02:41 and it succeeded.

[dnzbk]

Thank you, I'll test it. Please share such files via email next time.