GitHub Pages deployment stuck queued for days, even after cancelling and rerunning

[Mwest34]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Workflow Deployment

Discussion Details

Hi, I’m hoping someone can help get my Pages deployment unstuck. It started during the October 5 Actions outage and sat queued for days without getting a runner. I cancelled it today and reran all jobs once, but the new attempt is also queued with no jobs listed.

Repository: https://github.com/Mwest34/mwest_clock
Affected run: https://github.com/Mwest34/mwest_clock/actions/runs/37372819502 (pages build and deployment #40)
Current main commit: b1f2c2df85bb6c2d733b84c33636acc3069a779c

The run was created on October 5, 2026, at 20:56 UTC. The original build job (111973937491) never got a hosted runner. Its annotations included:

The job was not acquired by Runner of type hosted even after multiple attempts

Internal server error. Correlation ID: e8550132-3452-4af7-b3a0-19c04ca86ab8

A retry was accepted on October 5, but the run remained queued. Today, October 11, GitHub accepted the cancellation and then “Re-run all jobs.” The rerun was triggered around 20:49 UTC. At the latest check, the run API still reported queued, and the jobs endpoint returned total_count: 0 and jobs: []. I confirmed main had not advanced before rerunning it.

I also checked the repository settings: Actions are enabled, Pages deploys from main / (root), and the github-pages environment allows main with no required reviewers or wait timer. GitHub Status currently shows Actions and Pages as operational.

The previous successful deployment is still serving the site, but the latest fix on main has not deployed. I searched and found similar reports of queued runs with zero jobs, though cancellation did work in my case.

Could someone at GitHub investigate whether this run is stuck in scheduling, or suggest a safe way to get current main deployed? It’s frustrating to be blocked for days without a job starting or a useful error to act on. Thanks for any help.

[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. ⭐

[shirasu-bl-room]

Hello, I'm experiencing the same issue with GitHub Pages deployment.

My workflow's build and report-build-status jobs succeed, but the deploy job remains queued and the latest changes are not published. The GitHub Status page currently shows Actions and Pages as operational.

Has anyone found a workaround or received an update from GitHub about this issue?

Thank you!