GitHub Actions "Cannot find any run with the given ID" (download-artifact across workflows)

By Kaveh Alemi·Latchkey

Downloading an artifact produced by a different workflow run requires the correct run-id and a token with access to it. A wrong, stale, or inaccessible run-id resolves to no run.

What this error means

A download-artifact step that targets another workflow's run fails with "Cannot find any run with the given ID", even though the producing run exists in the UI.

Error: Cannot find any run with the given ID: 1234567890

Common causes

Wrong or stale run-id

The run-id passed does not point at the run that produced the artifact, or the run's artifacts have expired.

Token cannot read the source run

The artifact lives in another repo or workflow the GITHUB_TOKEN cannot access, so the run is not found.

How to fix it

Supply a valid run-id and access token

1. Resolve the real run-id of the producing workflow at download time.
2. Pass a token with read access to that run / repository.
3. Confirm the source artifacts have not expired by retention.

- uses: actions/download-artifact@v4
  with:
    name: build
    github-token: ${{ secrets.CROSS_REPO_TOKEN }}
    run-id: ${{ steps.find.outputs.run_id }}
    repository: ORG/other-repo

How to prevent it

• Resolve the producing run-id dynamically rather than hardcoding.
• Grant the download a token scoped to the source run.
• Account for artifact retention when downloading across runs.

Frequently asked questions

Related guides

References

• GitHub Actions documentation
• Workflow syntax for GitHub Actions