My GitHub Pages deployment is stuck, and my website is not updating.

[jablach3-spec]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Workflow Deployment

Discussion Details

My GitHub Pages deployment is stuck, and my website is not updating.

Repository: https://github.com/jablach3-spec/ssplitly.site-

Affected run: https://github.com/jablach3-spec/ssplitly.site-/actions/runs/37511386366

The initial build succeeded, but deployment displayed “waiting for github-pages deployment approval.” Required reviewers and the wait timer are disabled, and the main branch is allowed.

After cancelling and rerunning, the UI shows “Latest #2” and “Queued.” A subsequent API check reported run_attempt: 1, no jobs, and no pending deployments.

An earlier run (#159) failed with “The job was not acquired by Runner of type hosted even after multiple attempts” and an internal server error.

How can I recover this stuck run and deploy the latest commit?

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

[jovanovic-djo]

I can see that your site uses branch based Pages build (pages-build-deployment).
Last successful deploy was run #154 and every push since then (#155–#160) was cancelled or failed.

Things you can try:

1. Force-cancel the stuck run (a normal cancel doesn't clear a run with no jobs):
   gh api -X POST repos/jablach3-spec/ssplitly.site-/actions/runs/37511386366/force-cancel
2. Start a fresh build instead of re-runniny small commit (editing the README in theweb UI works), or run: gh api -X POST repos/jablach3-spec/ssplitl
3. If the new deployment shows "waiting" again, go to Settings -> Environments -> github-pages. Check that no deployment protection rule from a GitHub Ayment branches allows main.
4. If it is still stuck, go to Settings -> Pages, set the source to None, save, then set it back to main. This briefly unpublishes the site, but it resets the Pages pipeline.

Hope this helps.

[mdsuzon-hub]

The job logged CONCLUSION=abandoned. GitHub’s backend has already marked the deployment as dead, which is why the UI still shows “Queued” and the Cancel button does nothing.

Fix

1. Force-cancel the run (UI cancel button will fail)

gh api -X POST repos/OWNER/REPO/actions/runs/RUN_ID/force-cancel

2. Delete the abandoned deployment (Use API):

gh api repos/OWNER/REPO/deployments --jq '.[] | {id, environment, created_at}'
gh api -X DELETE repos/OWNER/REPO/deployments/DEPLOYMENT_ID

3. Reset Pages: Settings → Pages → Source = None → Save → wait 1 min → set Source back to GitHub Actions.

4. Push an empty commit to trigger a new deployment.

If it still won’t clear, open a support ticket and include the run ID plus the CONCLUSION: abandoned log line.