# Regarding the idle session timeout

**URL:** <https://community.auth0.com/t/regarding-the-idle-session-timeout/196515>\
**Category:** Get Help\
**Tags:** login-experience, new-universal-login-experience\
**Created:** [January 23, 2026, 10:25am UTC](https://community.auth0.com/t/regarding-the-idle-session-timeout/196515 "2026-01-23T10:25:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![chaitrk](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/chaitrk/32/70985_2.png) [@chaitrk](https://community.auth0.com/u/chaitrk)\
**Post date:** [January 23, 2026, 10:25am UTC](https://community.auth0.com/t/regarding-the-idle-session-timeout/196515/1 "2026-01-23T10:25:40Z")

</div>

Hi Team,

We have configured an persistent idle session timeout to be of 2 hours ,  
but after being inactive for more than 2 hours or long its giving an error stating” an error occurred during authorization flow, though as soon as after 2 hours it works , why after waiting for long time of inactivity we get “an error occurred during authorization flow” error. instead of logging out.

what could be issue here, any suggestions would helpful

Regards,  
Chaitra k.

---

<div class="post-metadata">

**Author:** ![gerald.czifra](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/gerald.czifra/32/75301_2.png) [@gerald.czifra](https://community.auth0.com/u/gerald.czifra)\
**Post date:** [January 23, 2026, 10:17pm UTC](https://community.auth0.com/t/regarding-the-idle-session-timeout/196515/3 "2026-01-23T22:17:04Z")

</div>

Hi @chaitrk

Thank you for reaching out to us!

Once the idle time of 2 hours is reached, the Auth0 session expires as intended, but if your application attempts a token exchange or silent authentication, the request is rejected because the session does not exist anymore. In this scenario, my assumption is that you do not have a redirection to the login screen implemented for such scenarios, hence why you are presented with the mentioned error message instead.

If the user interacts with your application after the 2 hour period, because the session has expired, the Auth0 server will likely return one of the following errors : `login_required` or `consent_required` and at this moment, if your application is not configured to catch these errors and explicitly trigger `logout()` or `loginWithRedirect()`, then you will receive the generic “an error occurred during authorization flow” error message.

My suggestion for fixing this behaviour would be to implement the logic in your application or SDK to catch the mentioned errors from the Auth0 server and trigger a redirect to the login page for the user.

I recommend reading through the following resources, as they can prove useful for further understanding such behaviours:

- [How to redirect user to login when token is expire](https://community.auth0.com/t/how-to-redirect-user-to-login-when-token-is-expire/119959);
- [Configure Silent Authentication](https://auth0.com/docs/authenticate/login/configure-silent-authentication);
- [Configure Session Lifetime](https://auth0.com/docs/manage-users/sessions/configure-session-lifetime);
- [Sessions](https://auth0.com/docs/manage-users/sessions)

Hope this helped!

Have a great one,  
Gerald

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [February 6, 2026, 10:17pm UTC](https://community.auth0.com/t/regarding-the-idle-session-timeout/196515/4 "2026-02-06T22:17:52Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.