Pages build and deployment queued for 10 hours and counting

[skibidibidop]

Select Topic Area

Bug

Body

Hi! I'd like to ask if anyone knows what to do here.

This is the repo: https://github.com/skibidibidop/progress

I tried to cancel the run but it fails every time
Github status says everything is okay
Attempts to push crash Neovim

[Blaz1kennBG]

+1. Im the same. I did see that github had some "red" stasuses and brushed it off but 10 hours after, github seems okay but the Action is still stuck haha

[yoannchaudet]

👋 I am following up with the Actions teams. This looks to be just a bad state following yesterday's outage. UPDATE: This is only a bad state in the system. It is not impacting other builds and deployments and will be cleared up automatically in the next 24 hours. You can just ignore this "queued" workflow for now.

A new commit on your repo should be triggering a new build properly. I did trigger on https://github.com/skibidibidop/progress/actions/runs/4325078564.

[skibidibidop]

Thank you very much!

[marcindulak]

Maybe in some cases queuing it's not due to an outage.

When a failed "pages-build-deployment" run is triggered manually using "Re-run jobs", it is queued instead of starting.
It may be a bug in "pages-build-deployment".

I experienced the following case.
First, fail a run of "pages-build-deployment", by disabling github actions, before the github pages are enabled.
Then enable github actions. Use "Re-run jobs" to trigger the run again manually, it is queued.
With the manually triggered run still queued, a new commit proceeds with an immediate "pages-build-deployment".

Example:

• manually triggered run, queued https://github.com/marcindulak/nba-teams-parallel-coordinates/actions/runs/12572158906
• commit triggered run, succeeded https://github.com/marcindulak/nba-teams-parallel-coordinates/actions/runs/12572240817

[marcindulak]

Another report of queued state in https://github.com/orgs/community/discussions/140404 (maybe there are more).

[marcindulak]

For reference: The problematic run is still queued, after 2 months.

And to repeat the solution mentioned by others: with the manually triggered run still queued, a new commit proceeds with an immediate "pages-build-deployment".

[JCG15]

Hola! a mi me pasa lo mismo, he intentado subir actualizaciones desde la aplicación del ordenador pero el workflow pages build and deployment se queda en Queued, he intentado subir una actualización hoy pero sigue igual y no se por qué puede ser, ayuda!!!

https://github.com/JCG15/JCG15.github.io/actions/runs/4555910424

[RanitManik]

It's March 1st, 2024, and I am facing the same issue now. All of my GitHub pages are being queued, and I can't cancel any workflow runs.

[jonathanandrade10]

+1. same issue here now

[vadimkantorov]

Same issue:

[Kaartik7]

I am facing the same issue, I have triggered and re-triggered the deployment but it still shows queued up since a while. Any fix around that?

[Galactic-Avenger]

hey man where you able to solve the problem I'm facing the same problem

[IzzyYCCheng]

2024.10.30 and the same issue still happen to me

[DarthFutuza]

Seeing the same. Looks like Github Actions being down is affecting page build/deployment as well, Github's status page is also not reporting the issue. 😢

[bray2sick]

Seeing the same. Looks like Github Actions being down is affecting page build/deployment as well, Github's status page is also not reporting the issue. 😢

Here I am wondering why my pages won't deploy.

[ErnestEnki]

Same thing on 16/Dec/2024

when I try to cancel the run, it says "Failed to cancel workflow."

I am not sure what else I can possibly do.

[rahulseetharaman]

Facing the same issue. Did you happen to resolve it @ErnestEnki ?

[ErnestEnki]

yes, after a lot of trial and error, I realized that there was no problem with my actions, what actually happened is that my account was shadow banned, that's why my actions wouldn't run.
I submitted a support ticket asking them to normalize my account, and they said it was because I had one of those alias emails that forwards to my real email, I did so for privacy and security concerns, but that gets you flagged. Once I changed my email to a more normal one, and submitted another ticket for them to verify, they reinstate my account and my actions again worked normally
not sure if it's the same for your case, but this was my case

[alexstanza]

I am facing the same issue here in 1 March 2025, how do I know if my account is shadow banned? and whether I should raise a support ticket?

[alexstanza]

I am facing the same issue here on 1 March 2025, I am confused whether I do anything wrong or I should just leave it there. A better guidance in a situation like this will improve the overall experience, since similar question has been posted since March 2023.

[pathak-aman]

Facing the same issue, 6th March 2025.

[wavky]

I re-ran a failed workflow, but it's still showing queued after 30 minutes. Other new deployments are also failing because of this workflow, and I can't cancel it.

[wavky]

After I pushed a new commit, the new workflow deployment succeeded, but the old one is still queued. I’m not sure why, but the result looks fine.

[engineering87]

Facing the same issue, 22th April 2025.
Trying everything but always failed deploy.

Run actions/deploy-pages@v4
Fetching artifact metadata for "github-pages" in this workflow run
Found 1 artifact(s)
Creating Pages deployment with payload:
{
	"artifact_id": 2981923710,
	"pages_build_version": "62047c5e9479cff27795520a0d7d4313b9072807",
	"oidc_token": "***"
}
Error: Creating Pages deployment failed
Error: HttpError: Deployment request failed for 62047c5e9479cff27795520a0d7d4313b9072807 due to in progress deployment. Please cancel b54578b92eb832e96ae99ff842f01ce18bfd0fc5 first or wait for it to complete.
    at /home/runner/work/_actions/actions/deploy-pages/v4/node_modules/@octokit/request/dist-node/index.js:124:1
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at createPagesDeployment (/home/runner/work/_actions/actions/deploy-pages/v4/src/internal/api-client.js:125:1)
    at Deployment.create (/home/runner/work/_actions/actions/deploy-pages/v4/src/internal/deployment.js:74:1)
    at main (/home/runner/work/_actions/actions/deploy-pages/v4/src/index.js:30:1)
Error: Error: Failed to create deployment (status: 400) with build version 62047c5e9479cff27795520a0d7d4313b9072807. Request ID B881:1EBFBC:2AB0E6F:2C0E3D3:6806C54F Responded with: Deployment request failed for 62047c5e9479cff27795520a0d7d4313b9072807 due to in progress deployment. Please cancel b54578b92eb832e96ae99ff842f01ce18bfd0fc5 first or wait for it to complete.

[DrakelingTech]

Same problem on 15 May 2025. I can deploy just fine in all repositories but one.

[qualityshepherd]

Same for me just now...

[qualityshepherd]

[laurogripa]

Same here today.

[wowamin]

[wowamin]

請問有人解決此問題了嗎?

[wowamin]

[wowamin]

https://github.com/all-age/allage/actions/runs/16308848228

[pretentiousgit]

I fixed this by going to Settings and futzing with the Pages settings.
I had it set to deploy from the main branch and it wanted me to set up a yaml config with workflows to do something instead.
Github provides the yaml automatically when you select "Deploy using actions" and adds it to a little .github/static.yml file.

When I ran it that way, the thing immediately deployed; if nothing else, you can try it.

[Sieo]

Still the same error. I have a jekyll-gh-pages.yml, I push onto the main branch, it build just fine, but can't deploy... I tried to cancel, queue, requeue, push, nothing seems to be working :/

Anyone got an idea ?

[mokurin000]

Seems Github pages deployment was broken again

[sentrychris]

This is becoming a recurring problem for me.

EDIT: This is getting worse. Every other deployment today looks like this:

---

EDIT 2: ...

[blu3fishez]

Same here. I'm facing that exact same issue as shown in the image.

[kallewesterling]

Same here -- last few days have been really bad :/

[epxzzy]

same here. it doesnt seem to resolve no matter what you do

[PiyalAhmed]

Seems like we are the fishes of the same pond. :')

[ctodd7977-rgb]

Why this problem can't be resolved

[IzzyYCCheng]

[laugh] Izzy YC Cheng reacted to your message:

…

________________________________ From: ctodd7977-rgb ***@***.***> Sent: Thursday, August 28, 2025 9:07:45 AM To: community/community ***@***.***> Cc: Izzy YC Cheng ***@***.***>; Comment ***@***.***> Subject: Re: [community/community] Pages build and deployment queued for 10 hours and counting (Discussion #49074) Why this problem can't be resolved — Reply to this email directly, view it on GitHub<#49074 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BCZSZ2WMLLLWQOQXOY35A2T3P3BGDAVCNFSM6AAAAAAVOOO3FWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMRUGMYTGNI>. You are receiving this because you commented.Message ID: ***@***.***>

___________________________________ The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. EY is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.