On this account, it seemed to be related to the session storage device being full:
It’s likely that this was fixed already.