GitHub Actions 'artifact not found' error usually stems from name mismatches or empty uploads

The error means actions/download-artifact searched for a matching artifact and found none, and by default that search covers only one run in one repository. A downstream job failing immediately is typical, and the producing job can still show green even when nothing was actually uploaded. Common causes include an upload glob that matched no files, matrix-suffixed artifact names that an exact-match download does not find, and artifacts belonging to a different run such as one triggered by workflow_run. Expired artifacts and artifacts written by deprecated version 3 are also possible causes. The suggested fix is to check the run's artifacts panel first, then align names or use the pattern input with merge-multiple.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in