I think this may be due to the brief delay after logging in where the current user is cached. @jorvis has it currently set to sleep for 500 ms before attempting to retrieve the current user, but perhaps that may not be enough time. Typically if user cannot be retrieved in that brief time frame, the page proceeds as if their is no logged in user.
I think this may be due to the brief delay after logging in where the current user is cached. @jorvis has it currently set to sleep for 500 ms before attempting to retrieve the current user, but perhaps that may not be enough time. Typically if user cannot be retrieved in that brief time frame, the page proceeds as if their is no logged in user.