Ok, the major issue is that the files are not UTF8 encoded. This actually causes an issue with version 2.0 and its new batching logic.Because of this none would import for me. perhaps your initial import was on a prior version of CSV Import. I counted 17 work numbers that might not have been imported due to the encoding.
A minor issue is that the CSV files also contained a blank column. This should not affect anything but does cause unnecessary processing.
Closely following the CSV file requirements and tips help ensure no issues during import.
Hope this helps!
ps. The next versions of Connections and CSV Import does include a couple minor tweaks so it should be a little more forgiving.