You can consider implementing a "Heartbeat" feature that helps with sliding session timeout time. Here's an example of how you can do it:
Insert a timing object (let's call it timing_1) into your application (Timing object).
In the Timer event of timing_1, add scripts that will perform a simple database operation, such as a SQL Select statement. This database operation will ensure that the session remains active.
Use the timing_1.Start(interval) method to start the timing object and specify the interval at which it should call the database operation. In this case, you can set the interval to every 3000 seconds (make sure it's less than the session timeout, which is 3600 seconds by default).
timing_1.Start(3000)
By implementing this "Heartbeat" feature, the application will regularly perform a database operation, ensuring that the session remains active and the Session ID stays valid while the user operates the application.
