ArgoCD
ArgoCD troubleshooting across the GitOps chain
Intellira reads application status, sync state and history read-only and explains why an app is OutOfSync or a sync failed — down to the manifest or commit behind it.
Sync & health signals
Reads operationState and per-resource messages to find the failing resource and the class of error.
GitOps correlation
Links drift or a failed apply to the manifest change and commit responsible.
Follows the chain
When a PreSync hook fails, it follows into the hook Job logs via the Kubernetes connector.
ArgoCD errors Intellira diagnoses
Browse all guides →Degraded
A Degraded ArgoCD app synced fine but a resource is unhealthy. Health — not sync — names the failing resource, and the app inherits the worst child health.
OutOfSync
An ArgoCD app shows OutOfSync when live cluster state deviates from the target state in Git. How to read the diff, find the real source of drift, and fix it.
ProgressingStuck
An ArgoCD app stuck Progressing is moving toward Healthy but never arrives. Sync status and health status are orthogonal — fix the workload, not the sync.
SyncFailed
When an ArgoCD sync fails, either the manifests never rendered or the apply errored. Read the operation message to find which, then the failing resource.
Common questions
OutOfSync vs Sync Failed — does it tell them apart?
See ArgoCD Analysis on your stack
Connect read-only and get an evidence-backed root cause on your next incident.