GitHub Pages deployments stuck in Queued for over 2 hours

[CodingWiz123-glitch]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Other

Discussion Details

Hello,

I'm having an issue with GitHub Pages deployments in my repository:

https://github.com/CodingWiz123-glitch/pixelcraft-web

My two most recent deployment workflows (#6 and #7) have been stuck in the Queued status for almost two hours.

Neither workflow has started running, and when I click on "All jobs," nothing appears.

I've also tried cancelling both workflows multiple times, but GitHub returns a cancellation failure.

My previous deployment (#5) completed successfully in 37 seconds, so I'm not sure why the newer deployments are stuck.

I've checked my repository settings:

• Actions permissions: Allow all actions and reusable workflows
• GitHub Pages source: Deploy from a branch
• Branch: main
• Folder: / (root)

Could you please investigate why these workflows are stuck and help me get my GitHub Pages deployments working again?

Thank you!

[yashh1323]

@CodingWiz123-glitch, first check whether your failed deploy started around 20:48 UTC on 11 November. GitHub had an Actions and Pages incident then, and recovery was reported by about 21:07 UTC, so a deploy that failed in that window may just need a re-run.

If it failed outside that window, toggling the Pages source has cleared stuck deployments for other people (
#212117,
#200823). In Settings → Pages, switch the source between “Deploy from a branch” and “GitHub Actions”, save, switch back, then push a new commit:

git commit --allow-empty -m "retrigger pages deployment"
git push origin main

Write down your current branch and folder first so you can restore them. It didn’t work for everyone: in
#201099 the poster had to unpublish the site, set the branch to None, wait a minute, then re-enable it.

[erkangcmn]

Hey, this isn't a problem with your settings. Your config (deploy from main / root) is fine, and #5 worked.

Runs #6 and #7 were created at 20:28 and 20:29 UTC on Nov 11, right in the middle of a GitHub incident that hit Actions and Pages ("Impact across multiple GitHub products including Actions, Pages, and Copilot products", see https://www.githubstatus.com/history). Runs that got queued during that window were left orphaned on GitHub's side. They never got any jobs, which is why "All jobs" is empty, and that's also why cancelling fails. Several other people hit the exact same thing at the same time (#212743, #212754, #212788).

You can't clear those two runs yourself, but you don't need to in order to get your site updated:

1. Leave #6 and #7 alone. Cancel/re-run won't work on them (it usually returns a 409).
2. Trigger a fresh Pages build with a new push. An empty commit is enough:

   git commit --allow-empty -m "Trigger GitHub Pages rebuild"
   git push

   Or without a commit:

   gh api -X POST repos/CodingWiz123-glitch/pixelcraft-web/pages/builds

3. Your Pages site currently shows as errored because of those runs. Once a new pages-build-deployment run finishes, it should go back to live.

If the new run also gets stuck in Queued, open a ticket at https://support.github.com (Actions) with the two run IDs (43096247542, 43096313130) so they can clear them on their end.

If this gets your site deploying again, mark it as the answer so others can find it 👍