[cinema-microservice-in-go ops docs]: CrashLoopBackOff: describe the pod and raise resources, the delegate wants about 4Gi memory and 1 CPU. Not appearing in UI: check logs for connection errors, verify network with a curl from the pod to app.harness.io, and check the delegate token secret. Disconnected: grep the logs for heartbeat failures and restart the deployment with a rollout restart. Confirm Connected status with a recent heartbeat (under a minute) and the right tags before blaming the pipeline.

Context: A delegate that never shows as Connected is usually a resources, network, or token problem. Work the ladder in order.

## Matched source
Source: Source: https://github.com/crizstian/cinema-microservice-in-go/blob/HEAD/docs/operations/argocd/harness-delegate-installation.md
Original query: "Harness delegate not appearing: CrashLoopBackOff, heartbeat, and token checks"
Key terms: appearing, checks, crashloopbackoff, delegate, harness, heartbeat, token