Are there any other timeouts on logged on sessions?
Unless otherwise arranged, all remote sessions are subject to timeouts which are explained below:
Disconnected Session Time Out: 15 Minutes
What this means:
When a user closes the last hosted application, the session goes into disconnected state, and it will be that way for 15 minutes, after which, the session will completely log off.
Example:
A user has Sage and Excel open in the hosted environment.
If the user closes Sage only, the session is still in active state.
When the user closes both Sage and Excel, the session will go into disconnected state.
That session will log off 15 minutes after the last application has been closed.
This feature can also be useful if a user happens to lose their internet connection on their workstation in the middle of a transaction, and as a result their hosted session gets disconnected.
In this case, the user can either move to a different workstation and login, or work on restoring their internet connection within the next 15 minutes. If successful, they can resume their transaction right where they left off.
Active Session Timeout: 24 Hours
What this means:
An active session is when a user is actively working in their hosted application, this can mean anything from mouse movement within the application, to actual navigation within the application.
A user is allowed to have an active session for 24 consecutive hours after which they are required to log off and log back on.
Example:
A user starts their session at 8:00AM.
The user goes to lunch at 12:00PM, and closes their hosted application. The session will go into disconnected state until 12:15PM, after which it is logged off.
If the user logs back on before 12:15PM, they can resume their session, and they are still on the 24 hour counter from 8:00AM, scheduled to be disconnected at 8:00AM the next morning**.
If the users reconnected at 1:00PM after coming back from lunch, their session would have already logged off, and their active session new timeout is 1:00PM the next day.**
**Please keep in mind that all server reboot nightly for backups and maintenance, so in this case, it is a possible that a user session might get disconnected before the timeout, if the maintenance schedule is reached before the timeout threshold.
Idle Session Timeout: 2 Hours
What this means:
If a user is away from their workstation or is not performing any activity on the hosted application for 2 hours, the session will get disconnected.
Activity can be as simple as mouse movement, and not necessary actively transacting.
Example:
A user walks away from their workstation for 2 hours. The session will go into disconnected state for 15 minutes, then log off after.
A user minimizes their hosted application for 2 hours, and the application is not in focus, meaning, the mouse may not travel over an active screen, the session will go into disconnect state for 15 minutes, then log off after.
Please note that it is HIGHLY ADVISABLE to actively close out any applications at the end of your day. Those will not be there the next morning, due to the nightly scheduled maintenance. Doing so will will also reduce the likelihood of data corruption due to abrupt logging off of idling sessions come maintenance time.