Agent remains red in Coupled status after connection is re-established

Current Situation :

When a Controller and Agent are already coupled, the underlying connection between them can subsequently be lost, for example due to a network interruption, firewall, load balancer, or proxy closing an idle connection.

However, when the connection is subsequently re-established and the Controller successfully receives and processes events from the Agent, there is no corresponding event/state update that informs the JOC Cockpit that the connection has been restored. Nevertheless, the JOC Cockpit continues to display the Coupled status in red.

This results in the JOC Cockpit displaying an outdated problem state even though communication between the Controller and Agent has been restored.

Workaround :

• Deploy or restart the Agents

Desired Behavior :

When the Controller successfully re-establishes communication with an already coupled Agent after a temporary connection loss, the Agent's status in the JOC Cockpit should be updated accordingly.