Since this didn’t make much sense (opening the file shouldn’t do anything, really), and you’re on a Litespeed server, I assume it was server caching causing the issue.
If it happens again, try to disable that server caching completely, then try again. If I had to guess, it would be that 🙂