GitHub Pages run 34749317180 stuck queued with 0 jobs after September 13 incident #207766
Replies: 2 comments
|
💬 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. ⭐ |
|
Update: both normal cancellation and force-cancellation now fail with the same HTTP 409 response. With the repository owner's approval and authenticated as berset88:
Both response bodies contain this exact message:
However, GET for this run still returns status queued, conclusion null, and updated_at 2026-09-13T09:19:14Z. There were zero jobs in the preceding check. This is a mismatch between the status reported by the read endpoint and the cancellation endpoints. A final check at 16:49:24 UTC still showed the run queued and the latest Pages build building. The latest recorded deployment remains the September 11 deployment, and the site returns HTTP 200 with Last-Modified September 11, 2026 16:10:50 UTC. No rerun or new Pages build has been requested because cancellation could not be confirmed. No repository files, secrets, visibility, or Pages configuration were changed. Can GitHub staff investigate this apparent stranded queue state and advise how to recover it? This update supersedes the original post's statement that API cancellation had not yet been attempted. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Pages
Body
Our branch-based GitHub Pages deployment remains queued with no jobs. Is there a known issue with runs created during the September 13, 2026 GitHub incident, and what is the safest recovery path?
Repository: https://github.com/Setyadi-House/orca-dashboard
Affected run: https://github.com/Setyadi-House/orca-dashboard/actions/runs/34749317180
Verified through the authenticated GitHub API at 2026-09-13 16:00:40 UTC:
The expected result is a completed build and deployment. Instead, there are no jobs or job logs available, and this update has not been deployed. The existing site still returned HTTP 200 when checked at 15:28 UTC. The latest recorded successful deployment was on September 11 at 16:10:56 UTC: https://github.com/Setyadi-House/orca-dashboard/actions/runs/34620432134.
GitHub's official incident feed records incident 0rn90wk115q9, affecting Actions and Pages among other services, from September 13 at approximately 09:16 UTC until 10:44:55 UTC. This run was created during that interval and remained queued more than five hours after the incident was resolved. A connection is suspected but not confirmed. Source: https://www.githubstatus.com/api/v2/incidents.json
An earlier browser cancellation attempt was reported to return “Failed to cancel workflow.” That failure has not been independently reproduced in this investigation. No cancel/force-cancel, rerun, or new build request was sent during the subsequent API investigation, and no repository or Pages settings were changed.
Has anyone recovered a similar Pages run with zero jobs after this incident? Guidance from GitHub staff on whether this queue entry needs investigation would be appreciated. Please advise before any cancellation, new build, or configuration change.
All reactions