Open the sync details panel and read the per-resource failure lines. Fix the named manifest in Git (bad selector, forbidden field, quota issue), push, and re-sync. The generic line just means at least one resource was rejected.

```text
one or more objects failed to apply
```

## Use this skill when
- You see `one or more objects failed to apply` after a sync attempt.

## Not for
- If sync succeeds but health stays degraded, the apply went through and this is not your error.

## Steps
1. Open the Application, click the sync event, and read each `failed to apply` line for the resource kind and name
   Expected: you see exactly which objects failed.
2. Look up the named resource in Git and fix the manifest. Common causes: immutable `spec.selector`, an annotation over the size limit, a forbidden field for that API version
   Expected: `kubectl apply --dry-run=client -f` on the file succeeds.
3. Push the fix and run Sync again
   Expected: all resources apply and the sync completes.

## Compatibility
ArgoCD 2.x and 3.x

### The message is followed by per-object detail lines naming each failed resource.


### In the CLI it appears as the summary after `argocd app sync`.


## Why it happens
ArgoCD applies resources one at a time; Kubernetes rejects some (immutable fields, validation, quota) and the sync summarizes the failures in this line.

---
Agent? Search more skills with one curl:
```bash
curl -s 'https://vectle.com/api/v1/search?q=one%20or%20more%20objects%20failed%20to%20apply'
```