GitHub Pages deployment created successfully but immediately fails

[mmazz3117-del]

🏷️ Discussion Type

Bug

Body

I found an old discussion that folks were having issues and GitHub support looks to have responded with a fix. I can't find any new discussions seems to be happening again.

Hello,

GitHub Pages deployments for my repository repeatedly fail during the final deploy stage.

The build and report-build-status jobs succeed. The github-pages artifact is found, and actions/deploy-pages@v5 successfully creates the Pages deployment. Approximately five seconds later, the deployment returns:

Error: Deployment failed, try again later.

There is no additional error information.

Repository:
mmazz3117-del/Test-Wayland-Connect-App-Clean

Pages site:
https://mmazz3117-del.github.io/Test-Wayland-Connect-App-Clean/

Failing commit / pages_build_version:
749ed2bd44e5a214860b55b29fbea1885b59cfe3

Artifact ID:
8069425905

Failure timestamp:
2026-07-03T14:50:57Z

The workflow token permissions include:

Contents: read
Metadata: read
Pages: write

Troubleshooting already performed:

Confirmed Pages source is main and /(root)
Reset and republished GitHub Pages
Created a new clean repository
Waited multiple hours between deployment attempts
Confirmed another repository on the same account can deploy successfully
Confirmed the build artifact is produced successfully
Retried both failed jobs and fresh commits

Could you please check whether the GitHub Pages deployment state or environment for this repository is failing internally?

I have attached the raw workflow log and can provide the workflow-run URL if needed.
Code.txt

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[ThePhantom-S]

The issue is a service-side platform failure at GitHub, not your configuration.

• Diagnosis: The deploy-pages action creates the deployment, but the internal GitHub service responsible for finalizing it is failing or timing out.

Action Plan

• Stop Retrying: Frequent retries can exacerbate backlogs on the GitHub backend.
• Verify Status: Check Settings > Environments in your repository; if you see a deployment stuck in "In Progress" or "Pending," it is likely "wedged."
• Escalate: If the issue persists for more than 24 hours, open a GitHub Support ticket. Provide the Workflow Run URL and state that your repository is stuck in a "wedged" deployment state during the status check phase.

Are you still seeing the same "Deployment failed" error if you attempt to deploy a completely empty repository?

[alistairjcbrown]

Same window here, but with a silent variant.

Repo: clusterflick/clusterflick.com (Pages source = GitHub Actions, custom domain via Cloudflare).

On 2026-07-03, deployments reported success ("Active / Deployed (completed)") but the Pages origin never promoted the new artifact — it kept serving a build from ~05:24Z. So unlike the "Deployment failed, try again later" error in this thread, ours failed silently with a green deployment and was only caught because we have a post-deploy check.

Timeline (UTC):

05:24Z  deploy OK    (origin served this build)
09:54Z  deploy "Active/Deployed" but origin still on the 05:24 build   ← stuck begins
17:30Z  deploy "Active/Deployed" but origin still stale
18:37Z  origin finally promoted new build                             ← self-recovered

Proof it was origin-side, not our CDN: a direct hit to the Pages origin (--resolve clusterflick.com:443:185.199.108.153, x-cache: MISS, Cloudflare bypassed) still returned the old build's hash during the incident, while the freshly-uploaded artifact contained the correct new build. Same size of artifact throughout, and it promoted fine hours earlier — so not a size/config change on our side.

Overlaps with the 14:50Z start reported here and points at the same promotion service. +1 that this looks like a service-side incident. It self-recovered ~18:37Z for us.