Skip to main content
An operator may open a task and then stay inactive for a long time. After a period of inactivity, that operator’s working session becomes inactive. Inactive sessions with open tasks can cause you to miss the processing targets specified in your SLA or delay the processing of entire batches. To prevent this from happening, you can specify a timeout period after which an inactive session will be automatically closed. All open sessions, both active and inactive, are displayed in the Administration and Monitoring Console in System Monitor → Sessions. You can specify a timeout on the following stations:
  • Verification Station (local or remote)
  • Data Verification Station (local or remote)
  • Project Setup Station (local)
  • Web Verification Station
  • Web Capture Station

Set timeouts on local and remote stations

A session becomes inactive when the operator has performed no actions for a set period. The Processing Server polls the Application Server every 60 minutes and deletes timed out sessions. If a timed out session holds an open task, that task returns to the general queue and the operator’s changes are lost. Each station can set a timeout locally, and the default is 15 minutes. To change it, modify the following registry key.
If the key is missing from the Windows registry on a given machine, add it and enter a timeout value. After a session becomes inactive, the timeout countdown begins on the Application Server. You can also set this timeout in IIS Manager, on the computer running the Application Server.
1

Open IIS Manager

Click Control Panel → System and Security → Administrative Tools → Internet Information Services (IIS) Manager.
Screenshot of the Internet Information Services (IIS) Manager being opened from the Windows Administrative Tools.
2

Open the Application Settings for the server

In IIS Manager, click Sites → Default Web Site → FlexiCapture12 → Server → Application Settings.
Screenshot of IIS Manager with the Server node of the FlexiCapture12 site selected, ready to open its Application Settings.
3

Set the timeout in minutes

Enter a value in minutes in the InactiveSessionTimeoutMinutes parameter. The default is 0. If the parameter is missing in IIS Manager, add it and then specify a value.
Screenshot of the IIS Manager Application Settings for the FlexiCapture12 Server showing the InactiveSessionTimeoutMinutes parameter and its value.
The timeouts for the Verification Stations, the Data Verification Stations, and the Project Setup Station live in the web.config file on the Application Server. Its default location is C:\inetpub\wwwroot\FlexiCapture12\Server\web.config, and any text editor can open it.

Set timeouts on web stations

On a web station, the countdown begins once the operator has performed no actions in the station’s browser window for a set period. The default is 120 minutes. The Processing Server polls the Application Server every 60 seconds and deletes timed out inactive sessions. You can change that polling period.
A web station timeout applies only to the Web Verification Station and the Web Capture Station.
Set the web station session timeout in IIS Manager, on the computer running the Application Server.
1

Open IIS Manager

Click Control Panel → System and Security → Administrative Tools → Internet Information Services (IIS) Manager.
2

Open the Application Settings for the Verification application

In IIS Manager, click Sites → Default Web Site → FlexiCapture12 → Verification → Application Settings.
Screenshot of IIS Manager with the Verification node of the FlexiCapture12 site selected, ready to open its Application Settings.
3

Modify the two session parameters

If either parameter is missing in IIS Manager, add it and then specify a value.
Screenshot of the IIS Manager Application Settings for the FlexiCapture12 Verification application showing the SessionInactiveLifetimeInMinutes and SessionRefreshInterval parameters.
The timeouts for the web stations live in the web.config file, by default at C:\inetpub\wwwroot\FlexiCapture12\Verification\Web.config. Any text editor can open it. After a web station times out, the user of that web station will be redirected to the login page. If an inactive session holds an open task, that task returns to the general queue. The Application Server saves every change the operator made, even if they never clicked Save. The next operator to pick the task up can accept or reject those changes.