This is usually caused by a dropped WebSocket connection between the agent's browser and the AsterCTI service. Ask the agent to refresh the page.
If the issue repeats, check whether a browser extension or firewall rule is blocking outbound WebSocket traffic.