Where can i find LOAD setting of 120 seconds.
The agent closes the browser, the browser crashes, or the agent clicks the Back button on the browser.
When you close the browser or navigate away from the Finesse desktop, the Finesse desktop makes a best-effort attempt to notify the server.
Finesse receives a presence notification of Unavailable from the client. Finesse waits 60 seconds, and then sends a forced logout request to the CTI server.
Race Conditions
The agent closes the browser window. Finesse receives a presence notification of Unavailable for the user. Finesse tries to sign the agent out; however, that agent is already signed out.
If the browser crashes, it can take the Finesse server up to 120 seconds to detect that the client is gone and send a presence notification to Finesse. A situation can occur where the client signs in to the secondary Finesse server before the primary Finesse server receives the presence notification caused by the browser crash. In this case, the agent may be signed out or put into Not Ready state on the secondary Finesse server.
If the Finesse desktop is running over a slower network connection, Finesse may not always receive an Unavailable presence notification from the client browser. In this situation, the behavior mimics a browser crash, as described in the preceding condition.
If agent is in Not Ready State before Failover, agent moves to Not Ready - Connection Failure after CTI Disconnect or Reconnect.
If agent is in Ready State before Failover, agent moves to Not Ready - Connection Failure upon his next state change to Not Ready.
... View more
