Alert pop ups are not appearing on the Multinode Orchestrator UI

News Knowledge Base
1

In multi node On-Prem Production Orchestrator cluster the alert popups are not appearing in the Orchestrator screen. However the alerts can be seen in Alerts TAB (bell icon) in Orchestrator UI.

Issue: In multi node On-Prem Production Orchestrator the alert popups are not appearing in the Orchestrator screen however the alerts can be seen in Alerts TAB (bell icon) in Orchestrator UI as shown in below image.



Resolution:

  1. Verify if the Orchestrator alerts are generating and reaching the alert icon
  2. WebSocket is responsible for getting alerts from the browser to pop up the alert message
  3. Ensure WebSocket is enabled at the site level with the following setup:
    1. IIS --> UiPath Orchestrator --> Configuration Editor --> system.webServer/webSocket
    2. Ensure that 'Enabled' is set to True. (See the screenshot below.)

  1. Check the logs from the developer console and analyze whether the WebSocket connection is being terminated by the load balancer
  2. After disconnecting the load balancer, check again; alert pop-ups should work in a single-node Orchestrator.



Next Action of Plan:

  • Coordinate with the Load Balancer team to configure additional settings related to WebSocket."

Explanation:

When logging into the Orchestrator, a WebSocket session is established, continuously monitoring alerts from the Orchestrator, as evident in the network trace. The Orchestrator triggers a popup display upon generating alerts.

In the case of a direct connection, the WebSocket is inherently enabled by both the client and server applications, ensuring unimpeded communication. However, in scenarios involving a multi-node load balancer situated between the server and client machines, the network load balancer possesses the capability to obstruct the WebSocket protocol. Consequently, the WebSocket initiates from the client side but encounters a hindrance in reaching the server, resulting in the failure to retrieve the data, and causing issues with the alert pop-up in the Orchestrator.


Each load balancer operates with its unique configuration, and to address potential complications, it is advisable to review any logs from the load balancer. However most of the scenarios customer's network team has access to it is hard to get the data. As a mitigation strategy, bypassing the load balancer connection and connecting the client to a single node can be attempted.