GitHub Pages deployment stuck in Queued state — cannot cancel

[3aMAuVn]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

GitHub Pages deployment stuck in Queued state — cannot cancel

Hello GitHub Community,

I am experiencing a GitHub Pages deployment problem.

GitHub username: 3aMAuVn

Repository: https://github.com/3aMAuVn/Attractive_Logo

Affected workflow: https://github.com/3aMAuVn/Attractive_Logo/actions/runs/42751225681

Workflow #8 has remained in the "Queued" state for more than six hours.

Previous deployment attempts failed with HTTP 400 and the error:

"Deployment request failed due to in progress deployment. Please cancel [the existing deployment] first or wait for it to complete."

When I attempt to cancel the workflow, GitHub displays:

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

The failed deployment is also marked "Active" in the deployment history.

An earlier deployment (#4) completed successfully, but subsequent deployments have failed.

Could someone please advise how to clear the stuck deployment or resolve the deployment conflict without deleting my existing GitHub Pages environment?

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

[helmipradita]

This happens because the internal GitHub Pages deployment environment (github-pages) is locked in an in_progress / Active state from the previous timed-out run.

Subsequent runs require exclusive access to deploy to the Pages environment, so the re-run remains perpetually in Queued waiting for the previous lock to clear. Because the re-run has not yet been assigned a runner job, the UI and API reject cancellation requests with "Cannot cancel a workflow run that is not in progress".

Here is how you can clear the stuck lock and resume deployments without deleting the repository or environment:

---

Method 1: The Settings Source Toggle (Fastest & Recommended)

Toggling the deployment source forcefully invalidates the active deployment lock in GitHub's backend:

1. In your repository (3aMAuVn/Attractive_Logo), navigate to Settings → Pages.
2. Under Build and deployment, click the Source dropdown and temporarily change it from Deploy from a branch to GitHub Actions (or change the branch selection to a non-existent temporary branch).
3. Click Save and wait 60 seconds for the backend to unregister the pending deployment lock.
4. Switch Source back to Deploy from a branch, select your branch (main / root), and click Save.
5. Trigger a fresh deployment with an empty commit from your local terminal:

   git commit --allow-empty -m "chore: re-trigger pages deployment"
   git push origin main

This supersedes the stuck run and initiates a clean build and deployment pipeline.

---

Method 2: Force-Clear via GitHub CLI / REST API

If you have gh CLI installed, you can manually mark the stale deployment as failed:

1. List recent deployments to find the stuck deployment ID:

   gh api repos/3aMAuVn/Attractive_Logo/deployments --jq ".[0] | {id: .id, environment: .environment, created_at: .created_at}"

2. Post a failure status to release the deployment lock (replace <DEPLOYMENT_ID> with the ID from step 1):

   gh api -X POST repos/3aMAuVn/Attractive_Logo/deployments/<DEPLOYMENT_ID>/statuses -f state=failure -f description="Cleared stuck deployment"

3. Once the stale deployment is marked as failed, push your new commit and the queue will process immediately.