GitHub Pages deployment #68 stuck in Queued – cancellation returns HTTP 409

[sergezehntner-ux]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Workflow Deployment

Discussion Details

Hello,

I'm experiencing a GitHub Pages deployment issue with my repository:

https://github.com/sergezehntner-ux/Mon_Ressenti

The "pages build and deployment" workflow run #68 is stuck or failing.

• Previous deployments UI broken on iOS Safari #66 and Adding modal type preview in notifications button. #67 completed successfully.
• The build and report-build-status jobs completed successfully.
• The deploy job remained in updating_pages status.
• After approximately 10 minutes, it failed with Error: Timeout reached, aborting!.
• A subsequent attempt remained queued for an unusually long time.
• I also encountered an HTTP 409 Conflict while trying to resolve the situation.

Could someone help investigate whether a stuck deployment or workflow state is preventing GitHub Pages from deploying normally?

Thank you for your assistance!

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

[sergezehntner-ux]

Update – Workflow #68 remains stuck and cannot be cancelled

The GitHub Pages deployment workflow #68 for repository "sergezehntner-ux/Mon_Ressenti" has been stuck in "queued" status since October 15, 2026.

When attempting to cancel it, GitHub displays:

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

I also checked the GitHub REST API directly. It still reports:

• Workflow run ID: "38770455540"
• Status: "queued"
• Conclusion: "null"
• Last updated: October 18, 2026, 14:19:31 UTC

This suggests a possible inconsistency between the workflow queue and cancellation handling.

Could GitHub Support investigate this stuck workflow and advise how to safely clear it without affecting the existing GitHub Pages site?

Thank you.

[slyyr]

Since the build jobs completed successfully, I'd focus on the deployment stage rather than changing the site's source code immediately.

Check the full logs for the deploy job and determine whether the failure occurs while waiting for deployment to begin or while publishing the Pages artifact.

Then verify the repository's Pages configuration and whether another deployment is running concurrently.

If the deployment remains stuck, retrying once after checking the logs may help establish whether the problem is transient. If repeated attempts fail at the same deployment stage, preserve the run IDs, timestamps, and complete error message for GitHub Support.

The updating_pages state and timeout alone don't establish the underlying cause.

If this helps resolve your issue, please mark this reply as the answer so others encountering the same deployment problem can find the troubleshooting steps!