GitHub Pages deployment stuck in queued state, cannot cancel, Pages status errored

[cordeliawnoble]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Workflow Deployment

Discussion Details

Hello GitHub Community,

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

Repository: https://github.com/cordeliawnoble/passerelletest

Pages URL: https://cordeliawnoble.github.io/passerelletest/

The GitHub Pages API reports status: errored and build_type: legacy.

A GitHub Actions workflow run is stuck in queued:

Workflow run ID: 38770018850

When attempting to cancel it using the GitHub CLI, I receive:

Cannot cancel a workflow run that is completed

However, the Actions API still reports:

status: queued
conclusion: null

A subsequent deployment failed with an error stating that another deployment was already in progress, referencing commit:

1c5d767ff1e56567e8fe7dbdcde88c6534d15be4

The associated deployment ID is 7098450482, whose latest deployment status is failure.

Other deployments have also failed, including:

7098790767

7099033811

Could you please investigate whether a stale GitHub Pages deployment lock or inconsistent workflow state is preventing new deployments, and help restore normal deployment functionality?

I would prefer to avoid changing the repository content or losing the current published site.

Thank you for your help.

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

[nipun-1234]

Hi,

This looks like a possible inconsistency between the workflow run status and the GitHub Pages deployment state.

I'd suggest checking the following before making any changes to the repository content:

1. Verify the workflow run: Open the Actions run directly and check whether it is still queued or appears completed in the GitHub UI. Compare this with the result from the GitHub CLI and API.
2. Check the deployment workflow: Review the workflow run logs and the repository's Pages settings to confirm whether the site uses a legacy publishing source or a GitHub Actions workflow.
3. Check for concurrent deployments: If the workflow uses a concurrency group, verify whether another run is holding up a new deployment. Avoid cancelling unrelated or active deployments.
4. Contact GitHub Support: If the run remains queued in the API but is reported as completed by the CLI, and new deployments continue to fail because another deployment is in progress, provide Support with the run ID, deployment IDs, commit SHA, and timestamps. They can investigate any backend state inconsistency that cannot be resolved through repository settings.

Since you want to preserve the current published site, I would avoid changing the publishing source or deleting deployment-related configuration until the cause is clearer.

Official documentation:

• GitHub Pages deployment: https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site
• GitHub Actions concurrency: https://docs.github.com/en/actions/using-jobs/using-concurrency

Hope this helps you narrow down the issue without risking the existing site.

[begobe1978]

I'm experiencing a very similar issue with GitHub Pages today (October 15, 2026).

Repository: https://github.com/begobe1978/begobe1978.github.io

Deployments #1–#4 succeeded normally.

Deployment #5 (workflow run ID 38770413389) completed its build successfully, but the Pages deployment stayed in updating_pages until it timed out.

The Actions API reports status: queued and conclusion: null. Both normal cancellation and force-cancellation return HTTP 409:

Cannot cancel a workflow re-run that has not yet queued.

I successfully cancelled the corresponding Pages deployment (ID 5972bb104729e4bb080a93e91e9e26ba6dda3402) using the API. Its status is now deployment_cancelled, but the Actions workflow remains queued.

I pushed another commit, triggering workflow #6, which is also queued.

The repository had been deploying successfully until today. This appears to be a similar GitHub Pages deployment or workflow scheduling issue.

Has anyone identified a workaround or received confirmation of an incident affecting GitHub Pages deployments?