Use case to display pipelines after a JCC node goes down

The use case pertains to the display of pipelines after the JCC node has stopped unexpectedly.

If there are multiple JCC nodes running, then a task with several instances is divided among them. For example, if we have an Ultra Task of nine instances, they will be split into three, each between the three JCC nodes. However, if any one of the nodes goes down, then the JCC state is not updated in the SLDB (Service Level Database). As a result, the JCC instance will remain in the RUNNING state, creating zombie instances on the Monitor.

The zombie instances are seen on the Monitor for a span of eight hours or until they reach the maximum heartbeat limit specified in the cleanup pipelines method. After the cleanup process is complete, the instances will no longer be visible on the Monitor.