GitHub Community
Pages build and deployment queued for 10 hours and counting #49074
-
Select Topic AreaBug BodyHi! 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 |
Beta Was this translation helpful? Give feedback.
Replies: 26 comments 49 replies
-
|
+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 |
Beta Was this translation helpful? Give feedback.
-
|
👋 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. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much! |
Beta Was this translation helpful? Give feedback.
-
|
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. I experienced the following case. Example:
|
Beta Was this translation helpful? Give feedback.
-
|
Another report of queued state in https://github.com/orgs/community/discussions/140404 (maybe there are more). |
Beta Was this translation helpful? Give feedback.
-
|
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".
|
Beta Was this translation helpful? Give feedback.
-
|
+1 this is still an issue for me as well with manually triggered runs still queued. |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/Lucoshi/Lucoshi-s-Video-Game-Palace/actions/runs/20275437285 |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
+1. same issue here now |
Beta Was this translation helpful? Give feedback.
-
|
Same issue: |
Beta Was this translation helpful? Give feedback.
-
|
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? |
Beta Was this translation helpful? Give feedback.
-
|
2024.10.30 and the same issue still happen to me |
Beta Was this translation helpful? Give feedback.
-
|
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. 😢 |
Beta Was this translation helpful? Give feedback.
-
Here I am wondering why my pages won't deploy. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
Facing the same issue. Did you happen to resolve it @ErnestEnki ? |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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? |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
Facing the same issue, 6th March 2025. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
Facing the same issue, 22th April 2025. |
Beta Was this translation helpful? Give feedback.
-
|
Same problem on 15 May 2025. I can deploy just fine in all repositories but one. |
Beta Was this translation helpful? Give feedback.
-
|
Same for me just now... 
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Same here today. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
請問有人解決此問題了嗎? |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/all-age/allage/actions/runs/16308848228 |
Beta Was this translation helpful? Give feedback.
-
|
I fixed this by going to Settings and futzing with the Pages settings. When I ran it that way, the thing immediately deployed; if nothing else, you can try it. |
Beta Was this translation helpful? Give feedback.
-
|
In my case at my time, this didn't fix it - the failing action ( |
Beta Was this translation helpful? Give feedback.
-
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 ? |
Beta Was this translation helpful? Give feedback.
-
|
Seems Github pages deployment was broken again |
Beta Was this translation helpful? Give feedback.
-
|
This is becoming a recurring problem for me. EDIT: This is getting worse. Every other deployment today looks like this: 
EDIT 2: ... 
|
Beta Was this translation helpful? Give feedback.
-
|
same here. it doesnt seem to resolve no matter what you do |
Beta Was this translation helpful? Give feedback.
-
|
Seems like we are the fishes of the same pond. :') |
Beta Was this translation helpful? Give feedback.
-
|
Why this problem can't be resolved |
Beta Was this translation helpful? Give feedback.
-
|
same here! |
Beta Was this translation helpful? Give feedback.
-
|
Same here, the problem came back? |
Beta Was this translation helpful? Give feedback.
-
|
[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.
|
Beta Was this translation helpful? Give feedback.
-
|
Still happening in dec 2025. |
Beta Was this translation helpful? Give feedback.
-
|
Doesn't seem like Github is interested in fixing the issue or even investigating it. |
Beta Was this translation helpful? Give feedback.
-
|
Still happening Jan 2026 4m 9s to deploy a single 41.9kb image file after redeploying a couple times.
|
Beta Was this translation helpful? Give feedback.
-
|
i faced the same issue, try to deploying to github pages |
Beta Was this translation helpful? Give feedback.
-
|
also seeing that my github pages run times out and fails, yet the status page says its functional; |
Beta Was this translation helpful? Give feedback.
-
|
Seeing same issue |
Beta Was this translation helpful? Give feedback.
-
|
Same issue |
Beta Was this translation helpful? Give feedback.
-
|
Same |
Beta Was this translation helpful? Give feedback.
-
|
Latest: Waited a few hours. Rerun. Job completed. Try this: https://omnixtar.github.io/moddadom/ ==== Came here to report the same problem: https://github.com/omnixtar/omnixtar.github.io/actions/runs/20967066462/job/60261614152 |
Beta Was this translation helpful? Give feedback.
-
|
I am facing the same problem, there must be an outage of some kind. |
Beta Was this translation helpful? Give feedback.
-
|
Had the same issue yesterday and today, yesterday just re-creating new content like 20 minutes later fixed the issue/got it onto a more stable runner, so far not so today. At least one today fully timed out after trying an failing deployment for 15 minutes. |
Beta Was this translation helpful? Give feedback.
-
|
Same problem exists today |
Beta Was this translation helpful? Give feedback.
-
|
yup.. |
Beta Was this translation helpful? Give feedback.
-
|
Yes me too |
Beta Was this translation helpful? Give feedback.
-
|
Oh Microsoft... |
Beta Was this translation helpful? Give feedback.
-
|
Igual |
Beta Was this translation helpful? Give feedback.
-
|
This got it going for me in short order. I was using the classic publishing method.
name: Deploy GitHub Pages
on:
push:
branches: ["main"] # or your default branch
workflow_dispatch:
permissions:
contents: read
pages: write
id-token: write
concurrency:
group: "pages"
cancel-in-progress: false
jobs:
build:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Setup Pages
uses: actions/configure-pages@v4
# Add your build steps here if needed
# For example, if using Jekyll:
# - name: Build with Jekyll
# uses: actions/jekyll-build-pages@v1
- name: Upload artifact
uses: actions/upload-pages-artifact@v3
with:
path: '.' # or your build output directory
deploy:
environment:
name: github-pages
url: ${{ steps.deployment. outputs.page_url }}
runs-on: ubuntu-latest
needs: build
steps:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v4
|
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
It worked twice in a row, but now I'm stuck again in a queue. It's fine. I have to go put a roast in the smoker, anyhow. |
Beta Was this translation helpful? Give feedback.
-
Doesn't the |
Beta Was this translation helpful? Give feedback.
-
|
... yup, I missed a warning because I was doing "panic change all the things". NVM and ty for the double-check! |
Beta Was this translation helpful? Give feedback.
-
|
If only the |
Beta Was this translation helpful? Give feedback.
and others
👋 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.