Yes... probably. I've seen many times this error in the q2a demo instance. I'm logged in and working. But when the scheduled offline job runs and "resets" the db (every hour), and I access to another page (sending my "old cookies"), I see this behaviour.
It looks like the user identified by the cookies in the browser is not anymore on the db...