Merge pull request #10656 from harness/delegate-disconnect

[PL-Doc] About Delegate Disconnect

Author: ivikramsahu

docs/faqs/harness-delegate-faqs.md

@@ -144,6 +144,14 @@ Developers often need to create delegates in multiple clusters in their environm
 
 For more information, go to [Automate delegate installation](../platform/delegates/install-delegates/automate-delegate-installation.md).
 
+### What happens when a delegate is disconnected?
+
+When a delegate is disconnected, Harness applies a Time-To-Live (TTL) policy:
+
+- Delegate – 6 hours: If a disconnected delegate doesn't reconnect within 6 hours, it is considered expired and will no longer appear on the Delegate page in the Harness UI.
+
+- Delegate Group – 7 days: If a delegate group has no active delegates for 7 consecutive days, the group is considered inactive and will be removed from the Harness UI.
+
 ## Delegate requirements
 
 ### What are the delegate system requirements?

docs/platform/delegates/delegate-concepts/delegate-registration.md

@@ -22,6 +22,16 @@ Once you have installed the delegate in your environment, select **Verify** in t
 
 This means Harness is waiting for the delegate you installed to register. Registration can take a few minutes. Once the delegate registers, the **Verify** screen will indicate that the delegate is running.
 
+:::danger Important Note
+
+After installation, if the delegate goes into a disconnected state, Harness applies a Time-To-Live (TTL) policy:
+
+- Delegate – 6 hours: If a delegate remains disconnected and does not send heartbeats for 6 hours, it is considered expired and will no longer appear on the Delegate page in Harness.
+
+- Delegate Group – 7 days: If no delegates in a group are active for 7 consecutive days, the entire group will be removed from the Delegate page in Harness.
+
+:::
+
 ### Verify delegate registration manually
 
 The Verify screen also includes troubleshooting steps. Here are a few of the steps for the Kubernetes delegate.