We're on APEX 24.2.11 on OCI. We're experiencing issues with the “Maximum Session Idle Time in Seconds” and “Session Timeout Warning in Seconds” settings at the Application/Shared Components/Security level which are impacting the session idle warning pop-up and session management. We're trying to set "Maximum Session Idle Time in Seconds" to 7200 and “Session Timeout Warning in Seconds” to 600. The goal is to have the session idle warning pop-up 10 mins before the session idle expiration which will occur at the two hour mark. Note the long idle time period of 1hr 50mins between the start of idle time and the time that the session should expire due to lack of activity.
The most troubling issue we're seeing is that when the session idle warning pop-up appears and you click "Extend", it causes the session to expire and the session timed out pop-up appears even though it's got over nine minutes left before the session should actually expire. This is problematic as it could cause a user to lose unsaved changes.
If I change the “Session Timeout Warning in Seconds” to 7140, which causes the warning pop-up to appear 60 seconds into idle time, clicking "Extend" works as expected. The session timed out pop-up doesn't appear and the user's session is extended. This would seem to indicate a bug with APEX's ability to handle a large idle time period.
A secondary/related issue is that the session expiration time value displayed in the session idle warning pop-up is not the expected session expiration time. Instead it's displaying the time that the pop-up was launched. For now we've gotten around this issue by altering the pop-up msg text to exclude displaying the expiration time (APEX.SESSION.ALERT.IDLE_WARN). Still, it's another indication that APEX is mishandling long idle time intervals before session idle expiration.
We'd really appreciate some help ASAP as users losing their changes due to session management issues is unacceptable.
Thx!