GitHub Actions run stuck queued for 12+ hours and blocks new workflow runs

[wallism]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

Subject: GitHub Actions run stuck queued for 12+ hours and blocks new workflow runs

Repository: wallism/rolesage
Workflow: Deploy RoleSage
Workflow file: .github/workflows/deploy-rolesage.yml
Workflow id: 224349318
Run URL: https://github.com/wallism/rolesage/actions/runs/26447411328
Run number: 328
Run id / databaseId: 26447411328
Event: workflow_run
Branch: master
Head SHA: 9a2b0f77a1231f8762d60fc76f7dc1591a5e3081
Created: 2026-05-26T10:40:13Z
Last updated: 2026-05-26T10:45:08Z
Current API status: queued
Current API conclusion: null

Problem:
This Actions run has been stuck in queued state for more than 12 hours. It appears to be an orphaned rerun state. The UI cannot cancel it, and new workflow runs are not starting even after pushing a new commit and renaming the workflow run name.

Observed API/CLI evidence:

• gh run view 26447411328 --repo wallism/rolesage shows status=queued, conclusion=null, jobs=[]
• gh api repos/wallism/rolesage/actions/runs/26447411328/jobs returns total_count=0
• gh run cancel 26447411328 --repo wallism/rolesage returns: Cannot cancel a workflow run that is completed
• gh api --method POST repos/wallism/rolesage/actions/runs/26447411328/force-cancel returns: 409 Cannot cancel a workflow re-run that has not yet queued
• gh run delete 26447411328 --repo wallism/rolesage returns: 403 Could not delete the workflow run

Attempted remediation:

• Tried cancel from GitHub UI.
• Tried rerun/cancel paths from GitHub CLI and REST API.
• Briefly disabled and re-enabled the workflow. Workflow is active again, but the run remains stuck queued.
• Pushed a new change and renamed the workflow run name, but new runs still do not start.

Context:
This started during the May 26, 2026 GitHub Actions incident where GitHub Status reported authentication issues leading to failure in starting Actions runs. The incident is now marked resolved, but this repository still appears blocked by the stuck run.

Request:
Please clear/cancel/delete the orphaned queued workflow run and unblock Actions scheduling for this repository.

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

[wallism]

I can't run any workflows and I've tried every option to resolve this myself, it needs a backend fix.
In terms of product improvement, allow delete run even when queued. that will allow users to unblock themselves.

[sanikolaev]

Same issue in https://github.com/manticoresoftware/manticoresearch/actions/runs/26410422028

[dozer75]

This came together with the outage yesterday, it has been reported in the initial thread for the outage as well (#196970), but not any responses from GitHub maintainers (surprise)...

[jgteam]

have the same issue, how did you resolve it?
:D

[dozer75]

No... It's still there...

[jgteam]

No... It's still there...

Ok... then I also will just wait it out until GitHub fixes it on their end...

[mark-wallis-apac]

yeah it auto resolved after a day or so (roughly). I had assumed it was a platform issue and they fixed whatever was going on...

[VURE-SATHVIK-22]

Hi,

This looks like an orphaned GitHub Actions queued run, especially since the run has no jobs and cannot be cancelled through the UI, CLI, or REST API.

Since you have already tried cancelling, force-cancelling, disabling/re-enabling the workflow, and pushing a new commit, this likely needs GitHub Support or a GitHub staff member to clear the stuck run from the backend.

I recommend opening a GitHub Support ticket and including the run ID, repository name, workflow name, API status, and the error messages you listed. Also mention that the issue started during the May 26 GitHub Actions incident and that new workflow runs are blocked.

Hopefully GitHub staff can manually clear the queued run and unblock scheduling for your repository.

[dozer75]

It's A LOT of people that has this problem after the 26th outage... GitHub should follow their own discussions and find a solution so not everyone needs to go through their lousy support...