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: 7 comments 4 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.
-
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.
-
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.
-
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.
👋 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.