Tech support just got back with me again. Here's there response:
As far as we're aware this issue is not common place to Javascript files, but actually is a common occurrence that has to do with the DNS Caching with the ISP's Name Server. Not sure what exactly causes it, but if it happens again just do the workaround of removing the file and then re uploading it.
That makes sense to me.