@Steven-Justin Ah it does seem to be a caching issue as @Kit-Bishop and yourself mentioned.

Try clearing the cache on your browser if this happens again.