This makes hard assumptions that there will never be a reproducible error that affects a single video file.  What if permissions are set wrong on the server?  Or the filename is incompatible with Windows?  Or any other of unexpected errors that would cause a single file to consistently fail, thus blocking any other video from being downloaded?

I don't understand why the previous logic was changed, in favor of this "blocking" logic.  With the automated "retry" clicking from the client, I don't see what problem is trying to be solved here.  And it's not described in the pull request, so ... no can compute :)