Replies: 3 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. ⭐ |
|
Update – GitHub Actions outage resolved, but workflow remains stuck I have now established that GitHub experienced an officially acknowledged service incident on 11 November 2026, affecting GitHub Actions and other services. According to the GitHub Status page:
However, my workflow run remains stuck. Affected run: Current observations:
This suggests that the run may have been left in an inconsistent state during the incident and was not recovered when the Actions backlog was processed. Could GitHub staff investigate this specific run and advise whether it needs to be cleared or reset internally? I would also appreciate confirmation that a new workflow run can be started safely without making changes to the project or workflow configuration. |
|
Same issue in public repository leinardi/make-common on GitHub Free. These runs remain queued on November 12:
Runs were created November 11 between 20:33 and 20:40 UTC, around the acknowledged Actions incident. The original CI run’s jobs API returned total_count: 0. Previous workflows completed successfully. Could GitHub staff investigate whether these runs were stranded during the incident and clear their internal queue state? EDIT |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Workflow Configuration
Discussion Details
Title: GitHub Actions workflow permanently stuck in queued state with zero jobs
I'm using GitHub Free with a private repository.
Repository: dazz01/endless-sky-accessibility-build
Workflow: Build Endless Sky Accessibility for Windows
Affected run: 65
Run ID: 43095108253
Run URL:
https://github.com/dazz01/endless-sky-accessibility-build/actions/runs/43095108253
The workflow has remained in the queued state since 11 November 2026 at 20:17 UTC.
The GitHub API reports:
The workflow uses GitHub-hosted Windows 2022 runners.
Earlier runs, including Builds 55 and 56, completed successfully. Subsequent runs failed because of workflow-file problems, which have since been corrected. Build 65 was accepted by GitHub but has never created a job.
My account is on the free plan. The billing page shows Actions storage usage of 0.2 GB out of 0.5 GB included. The repository's gross usage is displayed as $5.09, but I cannot establish whether this represents any chargeable usage.
Could someone investigate whether this run is stuck in an inconsistent internal queue state, and advise how it can be cleared?
I would also appreciate confirmation that my free Actions allowance is not preventing new jobs from starting.
All reactions