Harness "Failed to fetch ... manifest" from git in CI

Before a deploy, the delegate clones your manifests from git using the git connector. "Failed to fetch manifest" means that fetch failed: a bad branch or path, an auth failure, or the delegate could not reach the git host.

What this error means

A deploy stage fails early with "Failed to fetch manifest files from Git" citing a branch, path, or authentication error against the configured repository.

Harness

Failed to fetch files from git connector 'app-manifests':
branch: main, path: deploy/k8s
Error: Reference 'refs/heads/main' not found / path does not exist

Common causes

The branch or file path is wrong

The manifest reference points at a branch that does not exist or a path with no manifests, so the fetch returns nothing.

Git auth or reachability failed

The git connector credential is wrong/expired, or the delegate cannot reach the git host, so the clone fails.

How to fix it

Correct the branch and path

Confirm the branch exists and the manifest path is correct in the repo.
Update the manifest source in the service/environment to match.
Re-run the pipeline once the path resolves.

Fix the git connector credential and access

Ensure the git connector uses a valid token/SSH key from the secret manager and that the delegate can reach the git host.

How to prevent it

Keep manifest branch/path in sync with the repository layout.
Rotate git connector credentials before expiry.
Run delegates with reachability to your git host.