What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

When a user's login session expires after leaving MongoDB Atlas open for some time, the application may continue displaying its navigation bar and sidebar while the main content area becomes blank or displays an error. The interface does not clearly indicate that the session has expired, making it difficult to distinguish an authentication issue from an application failure or internet connectivity problem.

What would you like to see happen?

Describe the desired outcome or enhancement.

I would like MongoDB Atlas to handle expired sessions gracefully by clearly notifying users when their session expires and redirecting them to the login page when necessary. Alternatively, a visible session-expired message with a sign-in option would be helpful. If possible, the application should preserve the user's previous page so they can return to it after signing in again.

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

Clear session-expiration handling would improve the user experience, reduce confusion, and prevent users from mistakenly assuming that MongoDB Atlas is broken or that their internet connection is slow. It would also make the application feel more reliable and provide a clearer recovery path when authentication expires.

What steps, if any, are you taking today to manage this problem?

Currently, I have to refresh the page or navigate away and try again to determine whether the issue is caused by an expired session. Since the interface does not clearly communicate the session state, identifying the cause requires unnecessary troubleshooting.