Pages deploy stuck: run shows Queued but "Cannot cancel a workflow run that is not in progress" — tkre-tony/dashboard

[tkre-tony]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Workflow Deployment

Discussion Details

Repository: https://github.com/tkre-tony/dashboard (public, Free plan)
Custom domain: propertyatlas.sg
Workflow: pages-build-deployment (deploy from branch: main)

Since 7 Nov 2026 no Pages deployment has completed:

• #2348 (triggered 7 Nov 09:19 SGT / 01:19 UTC) sat in "Queued" for 20h 37m and never started. I cancelled it at 06:45 SGT on 8 Nov.
• #2349 (triggered 7 Nov 11:09 SGT / 03:09 UTC, commit b5d31f1) ran once: build and report-build-status succeeded, but actions/deploy-pages@v5 polled "Current status: syncing_files" for 10 minutes, then "Error: Timeout reached, aborting!" and cancelled the deployment.
  Attempt Welcome to GitHub product feedback #1 job: https://github.com/tkre-tony/dashboard/actions/runs/42323437052/job/128253213068
  Deployment ID / pages_build_version: 816a084e9f1edd370e80e7c0c70bc9b2a0ea6e83
• #2349 was re-run (attempt Feature Request: Select a column when adding an issue to a project #2, run 42332709511) at 21:15 SGT on 7 Nov. It still shows "Queued" at 09:14 SGT on 8 Nov, but "Cancel run" returns "Cannot cancel a workflow run that is not in progress". The run appears orphaned.

The previous run (#2347, 6 Nov) deployed normally in 53s. Site size and structure are unchanged, Actions usage is within the free allowance, and githubstatus.com shows all green.

Could GitHub staff please force-clear the orphaned run and any stale Pages deployment lock on the github-pages environment? Is there anything safe I can do on my side in the meantime?

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

[tkre-tony]

Update: a fresh commit to main at 09:52 SGT on 8 Nov triggered run #2350, which built and deployed normally in 36s, and later deploys are working too. Pages is working again for this repo.

#2349 attempt #2 (run 42332709511) still shows "Queued" and cannot be cancelled ("not in progress"), so it appears orphaned. It no longer blocks deploys, but staff may want to clear it.