GitHub Pages deployment stuck in Queued state and cannot be cancelled

[Leooszz29]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Workflow Deployment

Discussion Details

Hello,

I am experiencing an issue with GitHub Pages deployments in my repository:

Repository:
https://github.com/Leooszz29/meu-projeto

GitHub Pages site:
https://leooszz29.github.io/meu-projeto/

My GitHub Pages deployments started failing even though the build and report-build-status jobs complete successfully.

The deploy job reports the following error:

"Deployment request failed for 18c640c4fad2919b76dbe05354f82cf895184fe4 due to in progress deployment. Please cancel d4f30a1150f384f9d508f937131f31d930442917 first or wait for it to complete."

Affected workflow runs include:

#526
https://github.com/Leooszz29/meu-projeto/actions/runs/35882678203

#757
https://github.com/Leooszz29/meu-projeto/actions/runs/36737159442

Run #526 was previously stuck in Queued state. I was eventually able to cancel it successfully.

Run #757 is still reported as Queued after a re-run.

Before #526 was successfully cancelled, attempting to use "Cancel run" returned:

"Cannot cancel a workflow run that is not in progress."

The Deployments page also shows several consecutive failed GitHub Pages deployments (#754, #755, #756 and #757), while older deployments were successful.

The latest failed deployment is shown as "Active" on the All deployments page, even though it failed to deploy.

I checked the github-pages environment settings:

• Required reviewers: disabled
• Wait timer: disabled
• Deployment branch: main
• Administrators can bypass protection rules
• GitHub Actions are enabled
• GitHub Pages source: Deploy from a branch
• Branch: main
• Folder: /(root)

I also temporarily disabled and re-enabled GitHub Actions, but this did not clear the stuck deployment state.

The existing GitHub Pages site remains online using the last successful deployment, but new changes cannot be deployed.

It appears that GitHub Pages still considers deployment ID:

d4f30a1150f384f9d508f937131f31d930442917

to be in progress, although I cannot find any deployment visibly running in the GitHub UI.

Is there a way to clear or force-cancel this stale GitHub Pages deployment so that new deployments can proceed?

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

[bosmdavid-gif]

It looks like this has cleared on its own: the "pages build and deployment" runs on your repo from 1 Oct (around 19:55–20:28 UTC) all finished successfully, and your latest Pages deployment (d76c435) shows as success, so the site should be serving your newest commit now.

If it ever gets stuck again with "Please cancel <sha> first", you can cancel the stuck Pages deployment yourself. The endpoint accepts the commit SHA from that message:

gh api -X POST repos/Leooszz29/meu-projeto/pages/deployments/<sha>/cancel

If the workflow run itself is hanging, you can force-cancel it with gh api -X POST repos/Leooszz29/meu-projeto/actions/runs/<run_id>/force-cancel (the run id is in the URL of the run on the Actions tab). After that, push a new commit or re-run the workflow and it should deploy normally.

If that solves it, marking this as answered helps others who hit the same error.