CAB Workbench - Resume & Pause button not refreshing the pageDescriptionCAB Workbench Application issue - When clicking any UI action (Resume, start meeting, end meeting, Pause button and etc), the changes made on the CAB / change request is not reflected unless the page is refresh. This issue is only happening when the instance is connecting to the Load Balancer and is currently working as expected when connecting to normal nodes. 1. How CAB workbench work and how it is related to AMB When users click on any UI actions on CAB Workbench, browser makes REST call to server to update data at server side. The response from REST call is not used to update UI because there can be multiple CAB attendee and only one of them has made the REST call. Instead there is AMB connection established when CAB meeting page is open, and all related server side data updated is sent from server to browsers via AMB, and the data received via AMB is used to update UI.From zoom recording, there is no issues updating server side record although there was an 406 error when approving. (refreshing browser shows correct UI meaning server side data is updated correctly). Issue should be that the updated record data is not sent from server to browser via AMB. 2. How to test if the AMB is working while connecting to the Load Balancer: With load balancer: open same change_request in 2 browser tabs, update short description on one tab, the change request's short description from another tab is not updated. (showing record watcher/AMB not working). Without load balancer: short description is updated in the other tab(showing record watcher/AMB working) ***CAB is built based on AMB, if AMB doesn't work. we should involve the team that can work on load balancer. During the investigation, please kindly ask the customer to make sure that the Load Balancer is configured correctly based on KB0563731 before approaching LB team. ***More information about How AMB and Websockets architectural works can be found in KB0622691CauseWebsockets were blocked by firewall/proxy or not configured correctly. *** How to test if the Websocket is working as expected while connecting to Load Balancer or normal nodes: Access Websocket test page via the load balancer and via the direct node URL to see if there is any difference in the results?/$websocket_test.do would be the URL to access If the different results occur on Websocket test page while connecting to the Load Balancer, means that this issue is related to the Websockets and customer's Network Engineering team to check why Websocket isn't working via the load balancer path.ResolutionSetting/creating the system property " glide.cometd.websocket.enabled " and setting the value to False would fix the issue. This would make the communications use long-polling instead of Websockets. ***More information about the Websockets can be found in KB0829978 and KB0622691Additional InformationAll KBs related to this article: Load Balancer Configuration: KB0563731What is Websocket: KB0829978How AMB and Websockets architectural works: KB0622691