I think this is related to a session timeout. I have not been able to reproduce this behavior in a controlled way. Users of the platform will report this issue as an authentication error… but restarting their browser often works – however, sometimes they have to clear their cache as well.
Anyone else experience this as an ongoing issue?
