Skip to content
Latchkey

GitHub Actions "An action could not be found at the URI"

A uses: value resolves to a repo + ref + optional subpath that must contain an action.yml. If any part is wrong, GitHub cannot fetch the action and fails at startup.

What this error means

The run fails before jobs start with "An action could not be found at the URI" naming the uses reference, often after a typo, a deleted tag, or a wrong subdirectory.

github-actions
Error: An action could not be found at the URI 'https://api.github.com/repos/org/action/tarball/v9'

Common causes

Wrong ref or tag

The pinned tag/branch/SHA in uses does not exist (typo, deleted release), so the tarball URI 404s.

Missing action.yml at the path

A subdirectory uses reference points at a folder with no action.yml.

How to fix it

Correct the uses reference

  1. Verify the owner/repo and that the ref (tag/branch/SHA) exists.
  2. For a subdirectory action, ensure the path holds an action.yml.
  3. Pin to a known-good release or commit SHA.
.github/workflows/ci.yml
- uses: actions/setup-node@v4
# subdir action:
- uses: org/repo/.github/actions/build@v1

How to prevent it

  • Pin actions to existing tags or SHAs and keep them current.
  • Confirm subdirectory action paths contain action.yml.
  • Lint uses references so dead refs are caught early.

Frequently asked questions

What causes ""Action could not be found at the URI""?
The pinned tag/branch/SHA in uses does not exist (typo, deleted release), so the tarball URI 404s.
How do I fix "Action could not be found at the URI"?
Correct the uses reference

Related guides

References

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