Timeout setting in live environment works as following:
We’re using an expiry parameter that’s initially set when a user logs in. It’s currently set to 35 minutes.
This parameter has a sliding expiration, meaning that after 35 minutes, the expiry time will update if a full page load is performed. This includes transitioning from one page to another, refreshing the page, and so on, which will all trigger an update to the expiry time.
Once updated, the expiry is set again to 35 minutes, so the cycle continues.
It’s important to note that activity in the first 50% of the configured timeframe doesn’t force an update, which is why we mentioned 35 minutes. note this changes if we alter the configuration of the parameter.
The timeout within the test portal has been turned off currently until further notice.
The timeout in the live environment should be set to around 2100 seconds of inactivity on the form.
For the test environment, this has been turned off so there shouldn't be any timeout. If you're experiencing a timeout within the test environment, could you please confirm the time and date of your last test and the URL of the form you were testing?
Considering the above, if this is in the test environment, we'll need to complete testing to confirm what's causing a timeout after turning this setting off. So, please raise a new case online and provide the above information and we’ll investigate this further.