Jobs seem to be marked as completed prematurely

[PikeDev]

Using mongodump/restore as the mode. All collections were marked as downloaded correctly. About 60% were marked as uploaded. The job was marked as completed and did not continue uploading.

I manually flipped the "completed" flag to false in migrationjobs/list.json and resumed the job. In the log it shows a bunch of "added to upload queue" for the collections that weren't uploaded yet, but they do not get uploaded, instead the job flips the completed = true again.

[PikeDev]

Seems like it was caused by a collection that was either empty or non-existing. I think at that point it should be ignored/marked rather than silently stopping the whole job.