GitHub Pages deployment stuck in Queued / updating_pages, cannot cancel, deployment times out

[rentaolife-bit]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

Hello GitHub Community,

I’m experiencing a GitHub Pages deployment issue in my repository and would appreciate help investigating it.

Repository: https://github.com/rentaolife-bit/my-tech-lab
Pages URL: https://rentaolife-bit.github.io/my-tech-lab/
Branch: main
Latest commit: 5712881
Previous successful deployment commit: f0eea311f5bc56de3b14330162e6c3c0e458e1eb

1. Build succeeds, but deployment fails

In the pages build and deployment workflow:

• build completes successfully.
• report-build-status completes successfully.
• deploy fails.

The deployment log repeatedly reports:

Current status: updating_pages

It eventually times out:

Error: Timeout reached, aborting!
Canceling Pages deployment...

Deployment ID:

571288146c64f061b346056f39b5c78afddeb027

2. Workflow re-run remains stuck in Queued

After triggering Re-run once, the workflow has remained in Queued for several hours.

The original deployment attempt shows that the deploy job failed after approximately 10 minutes and 26 seconds.

When I try to cancel the workflow run, GitHub returns:

Cannot cancel a workflow run that is not in progress.

Refreshing the page does not resolve the issue.

3. GitHub Pages environment configuration checked

I checked the github-pages environment:

• Only the main branch is allowed to deploy.
• Required reviewers are not enabled.
• Wait timer is not enabled.

4. Possible wider service issue

I noticed several other users reporting similar GitHub Actions and Pages deployment problems in the community around the same time, including workflows stuck in Queued and Pages deployments failing or timing out.

GitHub Status history also showed resolved incidents involving Actions and Actions/Pages on November 4 UTC, around the time of my retry.

5. Questions

Could this issue be related to a stale Pages deployment, an inconsistent workflow state, or a GitHub Pages deployment backend problem?

Is there a safe way to restore normal deployment functionality without modifying repository content, deleting deployment records, or disrupting the last successfully published version?

I would appreciate any advice or confirmation from GitHub staff.

Thank you for your 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. ⭐

[joshua-lehmann]

Related observation from joshua-lehmann/cores3-apps today: we had a stale Pages deployment lock where cancellation returned “already finished.” Resetting Pages did not fix it. Switching our prebuilt site from custom Actions publishing to a dedicated gh-pages branch restored the existing URL, with two successful deployments.

Your report already mentions GitHub's managed pages build and deployment workflow, so our source-switch workaround may not apply to your case; both paths still depend on the Pages backend. I’m linking the diagnostic details and confirmed recovery here in case they help compare the incidents: https://github.com/orgs/community/discussions/211774#discussioncomment-19425317

Following for an upstream explanation or permanent fix, especially for sites already using branch publishing.