Actions runs stuck in queue; force-cancel returns HTTP 500

[Vladimir-Andreevich-core]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Actions Runner

Discussion Details

Hello.

Three GitHub Actions workflow runs in my repository are permanently stuck in the queued state and never receive a GitHub-hosted runner.

Repository:
Vladimir-Andreevich-core/lunaris-vault-base

Affected runs:

https://github.com/Vladimir-Andreevich-core/lunaris-vault-base/actions/runs/30705733159

https://github.com/Vladimir-Andreevich-core/lunaris-vault-base/actions/runs/30706707097

https://github.com/Vladimir-Andreevich-core/lunaris-vault-base/actions/runs/30707321884

No jobs start, no runners are assigned, and no logs are available.

Cancellation from the GitHub web interface returns:
Failed to cancel workflow.

The official force-cancel REST API also returns HTTP 500:

{
"message": "Failed to cancel workflow run",
"status": "500"
}

I disabled and re-enabled Actions for the repository, but the runs remain stuck.

Could a GitHub staff member please investigate and clear the stuck runs?

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

[Vladimir-Andreevich-core]

This is not a feature request or general product feedback. It is an active GitHub Actions service failure affecting my repository.

All three workflow runs remain permanently queued, no hosted runner is assigned, normal cancellation fails, and the official force-cancel API returns HTTP 500.

Could a GitHub moderator or staff member please escalate this to the GitHub Actions team and clear the stuck runs?

[Vladimir-Andreevich-core]

[Vladimir-Andreevich-core]

Update: there are now four permanently queued workflow runs:

https://github.com/Vladimir-Andreevich-core/lunaris-vault-base/actions/runs/30705733159

https://github.com/Vladimir-Andreevich-core/lunaris-vault-base/actions/runs/30706707097

https://github.com/Vladimir-Andreevich-core/lunaris-vault-base/actions/runs/30707321884

https://github.com/Vladimir-Andreevich-core/lunaris-vault-base/actions/runs/30710628939

Normal cancel returns HTTP 500.
Force-cancel returns HTTP 500.
Direct DELETE returns HTTP 403: "Could not delete the workflow run."

None of these runs receive a GitHub-hosted runner, and no job logs are created.

All available owner-side cancellation and deletion methods have been tested. This requires backend intervention from the GitHub Actions team.