GitHub Pages deployment #136 stuck in Queued for over 15 hours

[deepztoursandtravels]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

Hello GitHub Community,

My GitHub Pages deployment workflow #136 has been stuck in Queued status for more than 15 hours.

Details:

• Repository: https://github.com/deepztoursandtravels/deepz-tours-and-travels
• Branch: main
• Publishing source: Deploy from a branch
• Folder: /(root)
• Previous deployment #135 completed successfully in 51 seconds.
• Workflow #136 remains Queued even after re-running it.
• The deployment job has not started.

My website is still accessible, and all 9 newly uploaded SEO pages open through their direct URLs.

Could someone help identify why this Pages deployment is stuck in the queue and how to resolve it?

Thank you.

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

[helmipradita]

The reason workflow #136 has been stuck in Queued for over 15 hours (and re-running it does not start the job) is that GitHub Pages experienced a transient lease lock between workflow #135 and #136. When a Pages deployment run gets stuck prior to acquiring a runner, the runner never schedules jobs (leaving an empty jobs array), and subsequent re-runs will wait indefinitely for the prior environment lease to expire.

Here is the straightforward procedure to break the stuck queue and deploy your newly uploaded SEO pages:

---

Step 1: Reset the Pages Deployment Engine

1. Navigate to your repository: deepztoursandtravels/deepz-tours-and-travels.
2. Go to Settings → Pages (in the left sidebar).
3. Under Build and deployment, change the Source dropdown from Deploy from a branch to GitHub Actions.
4. Click Save and wait 1 minute. Switching the source forces the GitHub Pages controller to cancel and clear the active queue and release the stale lock on the github-pages environment.
5. Change the Source dropdown back to Deploy from a branch, verify that the branch is set to main and folder is /(root), then click Save.

---

Step 2: Spawn a Fresh Run (Avoid Re-running #136)

Do not use "Re-run" on workflow #136, as it is tied to the old queue state. Instead, push an empty trigger commit from your terminal:

git commit --allow-empty -m "chore: re-trigger pages deployment"
git push origin main

This will automatically launch workflow #137, which will bypass the stuck queue and complete the build and deployment normally.