Skip to content
Latchkey

GitHub Actions "Failed to download artifact" / artifact not found

download-artifact looked for an artifact by name in the current run and found nothing, almost always because the upload was skipped, the names differ, or it lives in a different run.

What this error means

The download step fails with "Failed to download artifact" or that no artifact matching the name was found, and the consuming job cannot proceed.

github-actions
Error: Failed to download artifact: Unable to find an artifact with the name: build-output

Common causes

Upload skipped or name mismatch

The producing job did not upload (it failed or was skipped) or used a different artifact name than the download expects.

Artifact is in another run

The artifact was created in a separate workflow run, so the same-run lookup finds nothing without cross-run configuration.

How to fix it

Match names and ordering

  1. Use identical name on upload-artifact and download-artifact.
  2. Ensure the producing job ran and succeeded before the consumer (needs:).
  3. For cross-run downloads, set run-id and a token.
.github/workflows/ci.yml
- uses: actions/download-artifact@v4
  with:
    name: build-output

How to prevent it

  • Keep upload/download artifact names in sync.
  • Order producing and consuming jobs with needs:.
  • Confirm the upload step actually ran.

Frequently asked questions

What causes ""Artifact not found""?
The producing job did not upload (it failed or was skipped) or used a different artifact name than the download expects.
How do I fix "Artifact not found"?
Match names and ordering

Related guides

References

Latchkey auto-heals failures like this one - detected, fixed, and retried without you. Start free → 30-day trial · No credit card