Stale resource state in Rancher UI during Cluster Agent latency

Rancher utilizes a local cache of downstream cluster resources to minimize direct API pressure on managed Kubernetes clusters. This synchronization depends on the cattle-cluster-agent pushing state updates to the Rancher management plane.

In environments with high network latency or intermittent agent connectivity, the Rancher UI may continue to display resources that have already been deleted or modified on the downstream cluster. This creates a discrepancy between the management plane's cached state and the actual cluster state.

Given the reliance on the reconciliation loop and event-driven updates, it is unclear how the system distinguishes between a healthy cluster with slow updates and a disconnected agent when determining the validity of cached data.

• What mechanisms are available to identify specifically which cached resources are stale without querying the downstream API directly?
• Does the Rancher management plane provide a configurable threshold to mark resources as potentially stale based on the last successful agent heartbeat?