/mcpThe actual behavior of the desktop under these conditions depends on the setting for Logout on Agent Disconnect (LOAD) in Unified CCE. The following table lists the conditions under which Finesse sends a forced logout to the CTI server: Race Conditions Server Action Desktop Behavior Scenario Finesse receives a presence notification of When you close the browser or The client closes, the 1. The agent closes the browser window. Finesse receives a presence notification Unavailable from the navigate away from the Finesse browser crashes, or the of Unavailable for the user. Finesse tries to sign the agent out; however, that agent is already signed out. client. Finesse waits 60 seconds, and then sends a forced logout request to the CTI server. desktop, the Finesse desktop makes a best-effort attempt agent clicks the Back button on the browser. 2. If the browser crashes, it can take the Finesse server up to 120 seconds to detect that the client is gone and send a to notify the server. 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. 3. 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. — Finesse receives a presence notification of — The client refreshes the browser Unavailable from the client. Finesse waits 60 seconds before sending a forced logout request to the CTI server to allow the browser to reconnect after the refresh. A situation can occur where the forced logout does not happen before the client The primary Finesse server receives a presence Because the connection to the The client encounters a signs in to the secondary Finesse server. If notification of Finesse server network glitch the agent is on a call, the primary Finesse Unavailable from the temporarily goes down, the client (Finesse is in service) server sends the forced logout request after the call ends. The agent is signed out or put client. Because Finesse is in service, it sends a fails over to the secondary Finesse server. into Not Ready state when the call ends, even though the client is already signed in to the secondary Finesse server. forced logout request to the CTI server for the agent. Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 379 Finesse High Availability Desktop Presence and Forced Logout