Intermittent "No artifacts named github-pages" when deploy-pages runs right after upload-pages-artifact in the same job
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions, javascript
- Domain
- ci-cd
Research direction
Start by tracing the artifact lookup in deploy-pages and the listArtifacts() call mentioned in the issue; compare the failing same-job workflow with a successful run. The issue suggests retrying empty lookups with backoff or using the upload action's artifact_id output, but does not identify files or tests. Done means the intermittent missing-artifact failure is handled without introducing duplicate-artifact failures.
Written by the indexing model from the issue text.
Description
When upload-pages-artifact and deploy-pages run in the same job, as in the static starter workflow, the artifact lookup can come back empty for an artifact that was finalized a fraction of a second earlier. The versions match (upload-pages-artifact v5.0.0, deploy-pages v5.0.1), so this is not the version mismatch discussed in #305.
From the failing job:
2026-10-07T13:43:59.4747863Z Artifact github-pages successfully finalized. Artifact ID 11486441618
2026-10-07T13:43:59.7518839Z Fetching artifact metadata for "github-pages" in this workflow run
2026-10-07T13:43:59.9097421Z Found 0 artifact(s)
Error: No artifacts named "github-pages" were found for this workflow run. Ensure artifacts are uploaded with actions/upload-artifact@v4 or later.
It is intermittent. That repository deployed 63 times with this layout and 62 runs found the artifact, 7 of them after a shorter gap between finalizing and listing (221–276 ms) than the failing run (277 ms). A new run of the same commit deployed normally.
Re-running, as the error message advises, cannot recover this layout: the re-run uploads a second github-pages artifact to the same run, and the lookup then fails with Multiple artifacts named "github-pages" were unexpectedly found for this workflow run. Artifact count is 2. (#338).
Possible fixes:
- When no artifact matches, retry
listArtifacts()a few times with a short backoff before failing. - Deploying by the
artifact_idthat upload-pages-artifact outputs (#399) would skip the lookup altogether. - The static starter is the only Pages starter that uploads and deploys in one job; the others upload in a separate build job, so the lookup happens seconds later. Moving the upload into an earlier job fixed it for us.
- Dominant language
- JavaScript
- Stars
- 967
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from actions/deploy-pages
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
actions/deploy-pages#454 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
actions/deploy-pages#435 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
actions/deploy-pages#434 · 3 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
actions/deploy-pages#418 · 19 comments · 12 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
actions/deploy-pages#416 ·
All issues in actions/deploy-pages
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
check:passed logos:edit
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
db-d1-sqlite: upsert is aliased to updateOne, so payload.kv.set never inserts new keysPossibly taken @pcbeingused333 claimed this today. OpenBug db: d1-sqlite Payload OSS
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
payloadcms/payload#19766 ·
Maintainers usually reply within 1 day
-
Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
inverse-inc/packetfence#9707 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
githubnext/gh-aw-workshop#5896 ·
Maintainers usually reply within 1 day