Its a server side problem, have been having the same issue for awhile (
api version 201605), awaiting a fix, hopefully soon. As you mentioned, the downloadUrl is relevant when getting the results, any time later, the batch moves on, this is at least how our system is designed.