This scenario assumes that the primary BlackBerry® Enterprise Server remains available and has an active connection to a BlackBerry Collaboration Service instance that is running, but the health score of the BlackBerry Collaboration Service instance fell below the failover threshold.

1. The BlackBerry Dispatcher sends a request to a BlackBerry Collaboration Service with an acceptable health score to promote its standby connection to an active conection.
2. The BlackBerry Collaboration Service with the acceptable health score promotes the connection to active.
3. The BlackBerry Dispatcher sends a request to the BlackBerry Collaboration Service instance with the low health score to demote the active connection to a standby connection.
4. When the BlackBerry Collaboration Service with the low health score receives the request, it finishes processing the packets that the BlackBerry Dispatcher sent to it previously.
5. The BlackBerry Collaboration Service with the low health score checks whether the standby BlackBerry Enterprise Server was promoted to the primary instance. In this scenario, it has not.
6. The BlackBerry Collaboration Service with the low health score sends a message to all open BlackBerry Collaboration Service sessions to log out.
7. The BlackBerry Collaboration Service with the active connection sends a message to all open sessions with collaboration clients to log in.
   One of the following events occurs:

   • If password caching is turned off, users must log in to the collaboration client manually. The session connects to the BlackBerry Collaboration Service with the active connection.
   • If password caching is turned on, users are logged in automatically. The sessions connect to the BlackBerry Collaboration Service with the active connection.