Seems to be fixed in the last update I did. Didn't pay attention to the last accessed field . When it happened ended up creating a new session. Would report if it occurs again