Replies: 7 comments 1 reply
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
|
Hello, I am experiencing the same GitHub Pages deployment issue. My repository: Affected workflow runs: 42165955254 42163343070 Both workflow runs remain stuck in QUEUED status. There are no runs in progress. When attempting to cancel the older run, I receive: HTTP 409 Previously, GitHub Pages deployment also failed with HTTP 504. Please investigate this issue and help resolve the stuck deployment state. Please preserve all existing website files and configurations. Thank you. |
|
Hello, I'm experiencing the same GitHub Pages deployment issue. My repository: https://github.com/chakriu212-lab/ORION Workflow run: https://github.com/chakriu212-lab/ORION/actions/runs/42088483688 The build job succeeds and creates the "github-pages" artifact (16.4 KB), but the deploy job repeatedly reports: "Current status: updating_pages" "Error: Timeout reached, aborting!" After retrying the failed deployment, the new run remains stuck in "Queued" with no jobs running. GitHub Status currently shows all systems operational. Could someone help investigate this stuck Pages deployment? Thank you. |
|
To resolve this on your own:
|
|
Same issue here. My repository is "Robandtom/Rob-tom-irrigation". Workflow "pages-build-deployment" run #110, latest attempt #2, is stuck queued with no jobs. The earlier Pages deployment timed out after repeatedly showing "syncing_files". When I try to cancel the queued retry, GitHub says, “Cannot cancel a workflow run that is not in progress.” My Support ticket was closed and directed me to community resources. Has anyone confirmed a safe way to clear this stuck Pages deployment? |
|
Same issue here.
It appears to time out and then returns an error. |
|
Hello, I’m experiencing a similar GitHub Pages deployment issue. Repository: https://github.com/orlintsvetanov/orlintsvetanov.github.io Workflow run: https://github.com/orlintsvetanov/orlintsvetanov.github.io/actions/runs/42263858878 The build succeeded, but deployment failed. After retrying, the run remains queued with no jobs. When I try to cancel it, GitHub says: “Cannot cancel a workflow run that is not in progress.” The updated files are in the repository, but the live site still shows the previous version. Could someone advise how to safely resume publishing? Thank you. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Workflow Deployment
Discussion Details
Hello, I’m trying to deploy GitHub Pages for obrien360/bp-toolkit. The build job succeeds, but deployment remains blocked by a stale deployment for commit
492c68b58843ef592605ac810c69d8a98c1737b7.The initial run (#20) built successfully, then its deploy job timed out while Pages was updating. A later run (#24) built successfully, but deployment failed immediately with: “Deployment request failed … due to in progress deployment. Please cancel 492c68b… first or wait for it to complete.”
I canceled the Pages deployment for that SHA using the Pages deployment API and confirmed the API returned
deployment_cancelled. However, deployment attempts still report that same SHA as in progress. Reruns of #20, #21, and #23 have been stuck in Queued with no jobs assigned for about five hours. The Actions UI says “Cannot cancel a workflow run that is not in progress.”Is there a way for a repository owner to clear this stale Pages deployment lock, or does it require GitHub staff to clear it? GitHub Status currently shows Actions and Pages operational.
Runs:
All reactions