GitHub Pages deployment stuck in Queued, cannot cancel or publish #212235
Unanswered
Mumtazcrypto
asked this question in
Actions
Replies: 1 comment
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Workflow Deployment
Discussion Details
Hello GitHub Community,
My GitHub Pages repository has three workflow runs stuck in "Queued", preventing updated content from being published.
Repository: https://github.com/mumtazcrypto/qrpybara-legal
Affected workflow runs:
#8: 42115627618
#9: 42118857250
#10: 42119157454
The build jobs succeeded, but Pages deployment failed with HTTP 400:
"Deployment request failed due to in progress deployment."
I canceled the blocking Pages deployment using the GitHub REST API, which returned HTTP 204 No Content.
However, the three workflow runs still appear as "Queued". Attempting to cancel them with GitHub CLI returns:
"Cannot cancel a workflow run that is completed."
The latest successful deployment is #7. My updated delete-account.html is committed to main, but the public GitHub Pages site still displays the previous version.
GitHub Status now reports all systems operational, but this repository remains stuck.
Could GitHub staff investigate the inconsistent workflow state and clear the orphaned Pages deployment or concurrency lock?
Please preserve the repository and its existing GitHub Pages URL.
Thank you.
All reactions