Ryan was running into an issue where he was still logged in but he was also getting unauthenticated error messages.
I believe I've found the source of the problem. When I changed login session timeout to 2 hours I must have accidentally changed the access token timeout to 30 hours (it was 30 minutes). This means that the browser would think that the token was still good after 2 hours since the token's timeout was 30 hours, but in actuality, the login session would have timed out after 2 hours. The access token timeout should be short compared to the login session timeout. I've now fixed it and here's a screen shot of the current configuration:
Ryan was running into an issue where he was still logged in but he was also getting unauthenticated error messages.
I believe I've found the source of the problem. When I changed login session timeout to 2 hours I must have accidentally changed the access token timeout to 30 hours (it was 30 minutes). This means that the browser would think that the token was still good after 2 hours since the token's timeout was 30 hours, but in actuality, the login session would have timed out after 2 hours. The access token timeout should be short compared to the login session timeout. I've now fixed it and here's a screen shot of the current configuration: