diff --git a/latest/ug/automode/auto-troubleshoot.adoc b/latest/ug/automode/auto-troubleshoot.adoc
index 5c299a17..d1eeb753 100644
--- a/latest/ug/automode/auto-troubleshoot.adoc
+++ b/latest/ug/automode/auto-troubleshoot.adoc
@@ -87,5 +87,23 @@ Look for errors related to your EKS cluster. Use the error messages to update yo
 
 //Ensure you are running the latest version of the {aws} CLI, eksctl, etc. 
 
+== Pod failing to schedule onto Auto Mode node
 
-📝 https://github.com/search?q=repo:awsdocs/amazon-eks-user-guide+[[auto-troubleshoot,&type=code[Edit this page on GitHub]
\ No newline at end of file
+If pods are not being scheduled onto an auto mode node, verify if your pod/deployment manifest has a **nodeSelector**. If a nodeSelector is present, please ensure it is using `eks.amazonaws.com/compute-type: auto` to allow it to be scheduled. See <<associate-workload>>.
+
+== Node not joining cluster
+
+Run `kubectl get nodeclaim` to check for nodeclaims that are Ready = False.
+
+Proceed to run `kubectl describe nodeclaim <node_claim>` and look under *Status* to find any issues preventing the node from joining the cluster.
+Some issues you may come across:
+
+- "Error getting launch template configs"
+
+You may receive this error if you are setting custom tags in the NodeClass with the default cluster IAM role permissions. See <<auto-learn-iam>>.
+
+- "Error creating fleet"
+
+There may be some authorization issue with calling the RunInstances API call. Check CloudTrail for errors and see <<auto-cluster-iam-role>> for the required IAM permissions.
+
+📝 https://github.com/search?q=repo:awsdocs/amazon-eks-user-guide+&#91;&#91;auto-troubleshoot,&type=code[Edit this page on GitHub]