# codecov/codecov-action "failed to properly upload report"

> Fix codecov/codecov-action "failed to properly upload report" from a transient upload failure or a missing token on private repos.

Source: https://latchkey.dev/learn/github-actions/codecov-action-failed-to-properly-upload-report  
Updated: 2026-06-26

codecov-action uploads coverage to Codecov. A transient network error, an upstream 5xx, or a missing token on private repos can fail the upload after tests pass.

## Diagnose it: is the job queued, or is the runner gone?

A job that never starts and a job whose runner disappeared mid-run look similar in the UI and have opposite causes. The first is a labelling or capacity problem, the second is the runner being killed, usually by memory pressure or a spot reclaim.

```.github/workflows/ci.yml
- name: Runner facts
  run: |
    echo "runner name: $RUNNER_NAME"
    echo "os/arch:     $RUNNER_OS/$RUNNER_ARCH"
    nproc; free -h; df -h /
    echo "labels this job asked for: ${{ toJSON(job) }}"
```

> If the job sits in `queued` and never picks up, no runner matches every label you listed. Labels are ANDed: `runs-on: [self-hosted, linux, gpu]` needs one runner carrying all three, not three runners carrying one each.

## The failures that are not your workflow

- Exit 137 is the kernel out-of-memory killer, not an application error. Check `free -h` above against your peak usage.
- Disk exhaustion presents as unrelated write errors deep in a build. GitHub-hosted runners ship roughly 14 GB of free space, which a Docker-heavy job can exhaust.
- A lost connection to the server on a self-hosted runner is usually the host being reclaimed or rebooted, not a network fault in your job.
- A job that starts and immediately fails with no step output normally failed during runner setup, before your workflow ran at all.

## FAQ

### What causes codecov/codecov-action "failed to properly upload report"?

There are 2 common causes: transient upload failure and missing token on private repo. A momentary network error or Codecov 5xx interrupts the upload.

### How do I fix codecov/codecov-action "failed to properly upload report"?

Supply the token and tolerate transient flakes. Set the token input to secrets.CODECOV_TOKEN for private repos.

### What does codecov/codecov-action "failed to properly upload report" actually mean?

The codecov step fails with "failed to properly upload report" though tests and coverage generation succeeded.

### How do I stop codecov/codecov-action "failed to properly upload report" happening again?

Provide CODECOV_TOKEN for private repositories. The prevention section lists 2 changes that keep it from recurring.

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt