GitHub Pages deploy stuck in updating_pages, then rerun queued for 8 hours

[elworks20240911-design]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Workflow Deployment

Discussion Details

My GitHub Pages build succeeds, but deployment times out. One retry of the failed jobs has now stayed queued for about eight hours.

• Public repository: https://github.com/elworks20240911-design/moriguchi-denki
• Affected run: https://github.com/elworks20240911-design/moriguchi-denki/actions/runs/41931633190
• Workflow: pages build and deployment (run number 39, branch main)

All times below are UTC.

1. The run started on 2026-11-04 at 23:10:57. Both build and report-build-status succeeded.
2. The deploy job used actions/deploy-pages@v5. The artifact was found and a Pages deployment was created at 23:11:17.
3. The log repeatedly showed Current status: updating_pages. At 23:21:33 it reported Timeout reached, aborting! and automatically canceled the Pages deployment.
4. I retried the failed jobs once at 23:22:32. At 2026-11-05 07:24 UTC, the run still reported status: queued, conclusion: null, and run_attempt: 1. There is no newer workflow run. I have not submitted more retries or tried canceling this queued run.
5. The public site still returns HTTP 200, but the homepage and six service pages retain the previous content. The preceding Pages run succeeded at approximately 22:49 UTC on November 4.

I found a similar report in https://github.com/orgs/community/discussions/212111, but do not know whether the cause is the same.

Could someone advise how to recover this queued run safely? Is there a known Pages deployment issue or a way for GitHub to investigate this run without disrupting the currently published site?

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