It's happening to some of us too. Not on every project though. We have been able to get around it by hitting refresh on that page.
This appears to be tied to browser cache. We had one other report of this happening and clearing cache and cookies resolved the issue. Will you please have your users seeing this behavior clear their cache and cookies if they are still seeing this behavior today? If this behavior persists please open a Support Case and we can take a closer look at this.