diff --git a/docs/send-data/kubernetes/troubleshoot-collection.md b/docs/send-data/kubernetes/troubleshoot-collection.md
index 8e78b1e96a..77842b7e21 100644
--- a/docs/send-data/kubernetes/troubleshoot-collection.md
+++ b/docs/send-data/kubernetes/troubleshoot-collection.md
@@ -912,6 +912,10 @@ Delete the pod forcefully by adding `--force --grace-period=0` to the `kubectl d
 
 If you are running the out of the box rancher monitoring setup, you cannot run our Prometheus operator alongside it. The Rancher Prometheus Operator setup will actually kill and permanently terminate our Prometheus Operator instance and will prevent the metrics system from coming up. If you have the Rancher prometheus operator setup running, they will have to use the UI to disable it before they can install our collection process.
 
+### unmarshal errors: field collector_selector not found in type config.Config
+
+This typically points to a schema (CRD) that’s out of date. Ensure you have the correct CRDs applied in the cluster.
+
 ### Falco and Google Kubernetes Engine (GKE)
 
 `Google Kubernetes Engine (GKE)` uses Container-Optimized OS (COS) as the default operating system for its worker node pools. COS is a security-enhanced operating system that limits access to certain parts of the underlying OS. Because of this security constraint, Falco cannot insert its kernel module to process events for system calls. However, COS provides the ability to use extended Berkeley Packet Filter (eBPF) to supply the stream of system calls to the Falco engine. eBPF is currently only supported on GKE and COS. For more information, see [Falco documentation](https://falco.org/docs/getting-started/third-party/#gke).