Webapp gets blank after an hour of idle session
Hi,
I’m encountering an issue with my development/twenty environment and could use some assistance. Here are the details:
Issue Description: When I leave the tab open in my development environment for about half an hour and then return, the site no longer functions. The page appears blank, and refreshing the page doesn’t resolve the issue.
Observations:
- There are no errors in the console.
- There are no network API calls or errors visible in the network tab.
Steps Taken:
- Attempted to refresh the page, but the issue persists.
- Checked the console and network tabs for errors, but found none.
Environment Details:
- Version: 0.23
6 Replies
The server is host in EC2 on Docker.
In order to get it running again, we've to clear the browser cookies. After that, it functioning well.
Weird, I'm trying to reproduce locally
Hey @charles, thanks for looking into this, I'll share the steps to reproduce locally anytime soon 🙂 .
Steps to Reproduce:
- Log in to the application with a valid user account.
- Leave the session idle for a while until the authentication token expires.
- Attempt to navigate or interact with the application after the token expiration.
- Observe the screen after the token has expired.
Description:
- After a period of inactivity, when the session token expires, the user is not redirected to the login page. Instead, a blank white screen appears, leaving the user stuck without any indication of the issue or the next steps. This disrupts the user experience and forces users to manually refresh or re-enter the URL, instead of being redirected to the login page to re-authenticate.
Are there maybe any server logs or errors in devtools about this?
Hi @ɃØĦɆᵾS ,
I’ve checked the network calls in the dev tools, and there’s only one call for getClientConfig. I’ve attached a screenshot for your reference. It shows an error, which may be causing the blank screen and not redirecting.
Additionally, I didn’t find any other console errors.
@anjali @Rishi S we have reworked our authentication guard, the issue should be solved on v0.30
Could you double check and re-open if needed